Triple
T7568660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hartford Civic Center |
E179183
|
entity |
| Predicate | collapsedRoof |
P58737
|
FINISHED |
| Object | 1978 |
—
|
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: 1978 | Statement: [Hartford Civic Center, collapsedRoof, 1978]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collapsedRoof Context triple: [Hartford Civic Center, collapsedRoof, 1978]
-
A.
collapsedOn
Indicates that one entity physically fell or caved in onto another entity, ending up resting on or covering it.
-
B.
roofCollapsed
chosen
Indicates that the roof of a structure has given way or fallen in, typically due to structural failure or external forces.
-
C.
collapsedWith
Indicates that one entity fell down or caved in together with another entity, typically as part of the same collapse event.
-
D.
collapsedDuring
Indicates that one entity structurally failed or fell down while another specified event or process was occurring.
-
E.
collapsedAfter
Indicates that one entity collapsed at some point in time after another specified event or entity’s collapse.
- 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_69c69f316e50819081a271c85c06f918 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f91d9bfc8190af6f5f8211c3dda2 |
completed | March 27, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69c6f4de77048190b8769e717fdcf8e7 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:51 p.m.