Triple
T3969813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Rock City |
E92300
|
entity |
| Predicate | disassembledAfter |
P53240
|
FINISHED |
| Object | end of Burning Man festival |
—
|
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: end of Burning Man festival | Statement: [Black Rock City, disassembledAfter, end of Burning Man festival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disassembledAfter Context triple: [Black Rock City, disassembledAfter, end of Burning Man festival]
-
A.
dismantledBy
Indicates that something has been taken apart, disassembled, or broken down by a particular agent or entity.
-
B.
partlyDismantledBy
Indicates that an entity has been only partially taken apart, removed, or deconstructed by another agent or process.
-
C.
reconstructedAfter
Indicates that one entity has been rebuilt, restored, or reassembled following the occurrence or existence of another entity or event.
-
D.
dissolutionFollowedBy
Indicates that one dissolution event occurs first and is directly succeeded by another specified event or state.
-
E.
abolishedAfter
Indicates that one entity was abolished at a later time than another entity was abolished.
- 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_69aed96624188190ac8c45bb57ab72b5 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaca33e4819091957c7915857a42 |
completed | March 9, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69aef8f252b081909749d40440d372b2 |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aefac8f7a48190b065487ce090eaf2 |
completed | March 9, 2026, 4:52 p.m. |
Created at: March 9, 2026, 3:32 p.m.