Triple
T6954434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crisis |
E161205
|
entity |
| Predicate | firstRunTimePeriod |
P74271
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [Crisis, firstRunTimePeriod, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstRunTimePeriod Context triple: [Crisis, firstRunTimePeriod, 2014]
-
A.
firstRunAt
Indicates the date and time at which an entity was first executed, launched, or run.
-
B.
firstTimeSince
Indicates that an event or state is occurring now after not having occurred since a specified prior time or reference event.
-
C.
primaryRuntime
Indicates the main runtime environment or platform under which an entity (such as a program, service, or component) is intended to execute.
-
D.
firstRunViewership
Indicates the number of viewers who watched a program during its initial (first) broadcast or release.
-
E.
firstSessionStart
Indicates the point in time when an entity’s very first session or interaction begins.
- 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_69c68852a9a0819097797e31d492e273 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dace1a94819095311e4288f01784 |
completed | March 27, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bf0a7c8190b5ed4aca22ba9b97 |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6dacb524c81909aade2282a4c0c01 |
completed | March 27, 2026, 7:30 p.m. |
Created at: March 27, 2026, 2:29 p.m.