Triple
T16477896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ai |
E400234
|
entity |
| Predicate | hasOutcomeInText |
P106752
|
FINISHED |
| Object | city burned |
—
|
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: city burned | Statement: [Ai, hasOutcomeInText, city burned]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutcomeInText Context triple: [Ai, hasOutcomeInText, city burned]
-
A.
hasOutcomeIndicator
Indicates that something is associated with a specific measure or indicator used to evaluate its outcome or results.
-
B.
hasEventOutcome
Indicates that a particular event results in, leads to, or is associated with a specific outcome.
-
C.
hasStatusInText
chosen
Indicates that a particular status or state is explicitly mentioned or described within a given text.
-
D.
hasNarrativeOutcome
Indicates that an event, action, or narrative element leads to or results in a particular story-related consequence or resolution.
-
E.
hasConclusion
Indicates that something leads to, results in, or is associated with a particular conclusion.
- 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_69d883813098819084f5409539723b59 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e0013ac8190b607d5f47d17c501 |
completed | April 18, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69e22706b0588190a48a951c5211a617 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:13 a.m.