Triple
T35094424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jean-Jacques Rouget |
E1012826
|
entity |
| Predicate | isManipulatedFor |
P182518
|
FINISHED |
| Object | his fortune |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: his fortune | Statement: [Jean-Jacques Rouget, isManipulatedFor, his fortune]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isManipulatedFor Context triple: [Jean-Jacques Rouget, isManipulatedFor, his fortune]
-
A.
isManipulative
Indicates that one entity exerts influence or control over another in a deceptive, exploitative, or unfair manner to achieve its own goals.
-
B.
manipulatedBy
Indicates that an entity is controlled, influenced, or operated by another entity, often in a deliberate or strategic manner.
-
C.
isManagedFor
Indicates that one entity is administered, overseen, or controlled on behalf of another entity or purpose.
-
D.
isManaged
Indicates that one entity exercises supervisory or administrative control over another entity.
-
E.
isManagedWith
Indicates that one entity is administered, controlled, or operated using another entity as the managing tool, method, or resource.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76dd432ec8190969bc32acfc152b1 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78dbf72648190a4971a558e9d1889 |
completed | May 3, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
| PDg | Predicate description generation | batch_69f78ce43094819093857fc99f269afe |
completed | May 3, 2026, 5:59 p.m. |
Created at: May 3, 2026, 4:01 p.m.