Triple
T32955982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Time Trax |
E843100
|
entity |
| Predicate | targetFugitivesOriginTime |
P196366
|
FINISHED |
| Object | future |
—
|
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: future | Statement: [Time Trax, targetFugitivesOriginTime, future]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetFugitivesOriginTime Context triple: [Time Trax, targetFugitivesOriginTime, future]
-
A.
timeOfInitiation
Indicates the specific point in time at which an action, event, or process begins.
-
B.
hijackingTimeApproximate
Indicates that the time at which a hijacking occurred is known only approximately rather than as an exact timestamp.
-
C.
fugitivePeriod
Indicates the time span during which an entity is considered a fugitive or actively evading capture or legal authority.
-
D.
timeOfDisappearance
Indicates the specific time at which an entity disappeared or was last observed to no longer be present.
-
E.
hasPerpetratorOrigin
Indicates that the origin or source of a perpetrator (such as their nationality, place of birth, or background) is associated with a particular event, action, or crime.
- 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_69f3494a31f481909057136e49b4fe60 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe2f078c24819082ba396b56f02808 |
completed | May 8, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69fe228fe1988190baf3bb34897f3dbe |
completed | May 8, 2026, 5:51 p.m. |
| PDg | Predicate description generation | batch_69fe2f066ac48190882c327b7e69e53f |
completed | May 8, 2026, 6:44 p.m. |
Created at: May 1, 2026, 1:21 a.m.