Triple
T30796271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pyne Gould Corporation (PGC) building |
E784236
|
entity |
| Predicate | statusAfter2011Earthquake |
P195645
|
FINISHED |
| Object | destroyed |
—
|
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: destroyed | Statement: [Pyne Gould Corporation (PGC) building, statusAfter2011Earthquake, destroyed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfter2011Earthquake Context triple: [Pyne Gould Corporation (PGC) building, statusAfter2011Earthquake, destroyed]
-
A.
statusAfter2015Earthquake
Indicates the condition or state of something following the 2015 earthquake.
-
B.
facedMajorEarthquake
Indicates that an entity has experienced or been subjected to a significant or severe earthquake event.
-
C.
populationImpact2010Earthquake
Indicates the effect or consequences that the 2010 earthquake had on a population, such as changes in size, distribution, or demographic characteristics.
-
D.
earthquakeDamageLevel2010
Indicates the severity or extent of damage caused by earthquakes in the year 2010.
-
E.
locationDuringEarthquake
Indicates the place where an entity is situated at the time an earthquake occurs.
- 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_69f224b2e2a48190b19aa43db9da5b67 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fddd373cdc8190be1b12e70e4deb1f |
completed | May 8, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69fddc6915a88190ad41e379aa3ede13 |
completed | May 8, 2026, 12:51 p.m. |
| PDg | Predicate description generation | batch_69fddd364c1481908794c9d423bdc2d7 |
completed | May 8, 2026, 12:55 p.m. |
Created at: April 29, 2026, 8:42 p.m.