Triple
T23726525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1983 Coalinga earthquake |
E586291
|
entity |
| Predicate | primaryEffects |
P1634
|
FINISHED |
| Object | building damage |
—
|
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: building damage | Statement: [1983 Coalinga earthquake, primaryEffects, building damage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryEffects Context triple: [1983 Coalinga earthquake, primaryEffects, building damage]
-
A.
primaryEffect
chosen
Indicates the main direct outcome or consequence that results from a given cause, action, or condition.
-
B.
primaryPower
Indicates that one entity serves as the main or dominant source of power or energy for another entity.
-
C.
primaryCharacteristics
Indicates the main defining traits or features that most fundamentally characterize an entity.
-
D.
ultimateEffect
Indicates the final or overall outcome that results from a preceding action, condition, or sequence of events.
-
E.
primaryDamageType
Indicates the main kind of harm or injury that an action, event, or object is responsible for causing.
- 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_69e24906fb108190a6898751e46bdc11 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b915a888819088e92f99711e8120 |
completed | April 29, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:08 p.m.