Triple
T36923258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert Fischer |
E913265
|
entity |
| Predicate | hasSubconsciousTargetedBy |
P201875
|
FINISHED |
| Object | Dom Cobb |
—
|
NE NERFINISHED |
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: Dom Cobb | Statement: [Robert Fischer, hasSubconsciousTargetedBy, Dom Cobb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubconsciousTargetedBy Context triple: [Robert Fischer, hasSubconsciousTargetedBy, Dom Cobb]
-
A.
targetedBecauseOf
Indicates that one entity is made a target of an action, harm, or scrutiny specifically due to possessing a particular attribute, identity, or characteristic.
-
B.
hasTarget
Indicates that one entity is directed toward, aimed at, or intended to affect another specific entity as its target.
-
C.
wasTargetDuring
Indicates that an entity served as the target of another entity or action during a specified time period or event.
-
D.
usesTarget
Indicates that one entity employs, applies, or operates on another entity as its target or object of action.
-
E.
hasInvestigationTarget
Indicates that an investigation is directed toward or focused on a particular target entity.
- 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_69f76e885b848190bad82c87e9525486 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a002dd4066c8190945a09ed82f44f3f |
completed | May 10, 2026, 7:03 a.m. |
| PD | Predicate disambiguation | batch_6a002b141f4081909999e14988105f3a |
completed | May 10, 2026, 6:52 a.m. |
| PDg | Predicate description generation | batch_6a002dd3294881909e860157fc459a85 |
completed | May 10, 2026, 7:03 a.m. |
Created at: May 3, 2026, 4:13 p.m.