Triple
T16525313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Enemy |
E401418
|
entity |
| Predicate | placeInJackReacherTimeline |
P81955
|
FINISHED |
| Object | prequel to Killing Floor |
—
|
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: prequel to Killing Floor | Statement: [The Enemy, placeInJackReacherTimeline, prequel to Killing Floor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeInJackReacherTimeline Context triple: [The Enemy, placeInJackReacherTimeline, prequel to Killing Floor]
-
A.
operatorAtTimeOfDisappearance
Indicates that an operator was responsible for or in control of something at the specific time when a disappearance occurred.
-
B.
inceptionWithin
Indicates that one event, process, or entity begins or is initiated entirely within the temporal or spatial bounds of another.
-
C.
timeInOfficeBeforeAssassination
Indicates the duration an individual held office prior to being assassinated.
-
D.
locatedInTimeBefore
chosen
Indicates that one temporal event or interval occurs entirely before another in time.
-
E.
positionInFBI
Indicates that one entity holds a specific role or position within the organizational structure of the FBI.
- F. None of above.
Provenance (3 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32ed323c081908218460aa4ae3cf6 |
completed | April 18, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69e296995d388190b88ebe189dce890d |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.