Triple
T30579933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ground Zero |
E778355
|
entity |
| Predicate | rebuildingBegan |
P16795
|
FINISHED |
| Object | 2002 |
—
|
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: 2002 | Statement: [Ground Zero, rebuildingBegan, 2002]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rebuildingBegan Context triple: [Ground Zero, rebuildingBegan, 2002]
-
A.
rebuild
Indicates restoring or constructing again something that was previously built, often after damage, destruction, or significant alteration.
-
B.
reconstructionStart
chosen
Indicates the point in time or event at which a reconstruction process or activity begins.
-
C.
majorRebuildCompleted
Indicates that a significant reconstruction or overhaul of an entity has been fully completed.
-
D.
rebuiltAfterEvent
Indicates that an entity was reconstructed or restored following a specific event that caused damage, destruction, or significant alteration.
-
E.
restorationBeganWith
Indicates that the initiation of a restoration process started with or was triggered by a specified prior event, action, or condition.
- 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_69f224a04b248190b0ca443ec86207b8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:23 p.m.