Triple
T29467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1906 San Francisco earthquake |
E588
|
entity |
| Predicate | magnitude |
P1937
|
FINISHED |
| Object | 7.8 |
—
|
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: 7.8 | Statement: [1906 San Francisco earthquake, magnitude, 7.8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: magnitude Context triple: [1906 San Francisco earthquake, magnitude, 7.8]
-
A.
length
Indicates a measurement relationship where a value specifies how long something is from one end to the other.
-
B.
significance
Indicates that one entity holds particular importance, influence, or meaningful impact in relation to another entity or context.
-
C.
volume
Indicates the amount of three-dimensional space an entity occupies or contains.
-
D.
weight
Indicates a relationship where a numerical value quantifies how heavy an entity is, often used to measure or compare mass or load.
-
E.
width
Indicates the measurement of how wide an entity is, typically the extent of its horizontal dimension from side to side.
- 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_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. |
| PDg | Predicate description generation | batch_69a248fef2b881908180bd4e32e58cb5 |
completed | Feb. 28, 2026, 1:46 a.m. |
Created at: Feb. 28, 2026, 1:44 a.m.