Triple
T29475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1906 San Francisco earthquake |
E588
|
entity |
| Predicate | caused |
P694
|
FINISHED |
| Object | fires in San Francisco |
—
|
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: fires in San Francisco | Statement: [1906 San Francisco earthquake, caused, fires in San Francisco]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: caused Context triple: [1906 San Francisco earthquake, caused, fires in San Francisco]
-
A.
causeOf
chosen
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
B.
hasCause
Indicates that one entity is the reason for, or brings about, the occurrence or existence of another entity or event.
-
C.
triggered
Indicates that one entity causes an event, action, or process involving another entity to start or occur.
-
D.
considered
Indicates that one entity regards, judges, or thinks about another entity in a particular way or context.
-
E.
after
Indicates that one event, state, or action occurs later in time than another, following it in temporal order.
- 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_69a2479dec388190967ba648663442c9 |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a2490019948190a89bb0910c60d462 |
completed | Feb. 28, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69a2486d40348190b2d21fc444f499a6 |
completed | Feb. 28, 2026, 1:44 a.m. |
Created at: Feb. 28, 2026, 1:44 a.m.