Triple
T2995191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Westworld |
E81048
|
entity |
| Predicate | endOfOriginalRun |
P44889
|
FINISHED |
| Object | 2022-08-14 |
—
|
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: 2022-08-14 | Statement: [Westworld, endOfOriginalRun, 2022-08-14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endOfOriginalRun Context triple: [Westworld, endOfOriginalRun, 2022-08-14]
-
A.
originalRunOnABCEnd
Indicates that an original run or execution of something concludes or terminates at the end of an ABC sequence or ABC-designated segment.
-
B.
originalRunStatus
Indicates the initial or prior execution state of a run before any subsequent updates or changes.
-
C.
endOfRuleContext
Indicates that a particular parsing or evaluation rule has reached its terminating boundary within the current context.
-
D.
endRule
Indicates that a previously active rule, regulation, or governing condition is terminated or ceases to apply.
-
E.
canonicalOrderEnd
Indicates the point or boundary at which a defined canonical or standard ordering of elements, events, or components concludes.
- 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_69ad8b187fc8819085914d3c9ea3142d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99f2e5888190b3346012e2578dab |
completed | March 8, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69ad9615fefc8190ad96da92519cb7a3 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97ba55dc8190b6dddddfb751cf64 |
completed | March 8, 2026, 3:37 p.m. |
Created at: March 8, 2026, 2:59 p.m.