Triple
T659264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Carolina State Capitol |
E11717
|
entity |
| Predicate | destroyedPredecessorBy |
P1512
|
FINISHED |
| Object | fire of 1831 |
—
|
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: fire of 1831 | Statement: [North Carolina State Capitol, destroyedPredecessorBy, fire of 1831]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: destroyedPredecessorBy Context triple: [North Carolina State Capitol, destroyedPredecessorBy, fire of 1831]
-
A.
predecessorDestroyed
chosen
Indicates that one entity has caused the destruction or elimination of another entity that existed or acted before it.
-
B.
predecessor
Indicates that one entity comes before another in an ordered sequence or succession.
-
C.
predecessorStateDefeated
Indicates that a prior state or governing entity was defeated or overcome, typically in a political or military context.
-
D.
destroyedDuring
Indicates that one entity was destroyed in the course of, or as a consequence of, a specified event or time period.
-
E.
cededFrom
Indicates that control, ownership, or sovereignty over something was transferred away from a source entity to another entity, typically through a formal or legal act of cession.
- 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_69a4932862a0819098be659c814e4981 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a0f55f7481909e052a25bd12d455 |
completed | March 1, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69a49d1406ec8190abf546549264c85d |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.