Triple
T29499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1906 San Francisco earthquake |
E588
|
entity |
| Predicate | inspiredTheory |
P119
|
FINISHED |
| Object | elastic rebound theory |
—
|
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: elastic rebound theory | Statement: [1906 San Francisco earthquake, inspiredTheory, elastic rebound theory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inspiredTheory Context triple: [1906 San Francisco earthquake, inspiredTheory, elastic rebound theory]
-
A.
theorized
chosen
Indicates that one entity has proposed or developed a theoretical explanation or hypothesis about another entity or phenomenon.
-
B.
coreIdea
Indicates the central concept or primary message that underlies or unifies something, such as a text, argument, or work.
-
C.
inspiredSettlement
Indicates that one entity’s ideas, actions, or example motivated or influenced the creation, development, or characteristics of a particular settlement.
-
D.
introducedConcept
Indicates that one entity is responsible for presenting, defining, or bringing a new concept into use or awareness for another entity or context.
-
E.
proposes
Indicates that one entity formally suggests or puts forward an idea, plan, or course of action to another entity for consideration or approval.
- 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.