Triple
T10107316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Francisco volcanic field |
E216352
|
entity |
| Predicate | youngestEruptionsAge |
P54977
|
FINISHED |
| Object | about 900 years ago |
—
|
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: about 900 years ago | Statement: [San Francisco volcanic field, youngestEruptionsAge, about 900 years ago]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: youngestEruptionsAge Context triple: [San Francisco volcanic field, youngestEruptionsAge, about 900 years ago]
-
A.
notableEruptionAge
Indicates the age or time period at which a notable volcanic eruption associated with an entity occurred.
-
B.
lastEruption
Indicates the time or event corresponding to the most recent eruption associated with a given entity.
-
C.
lastEruptionApproximateDate
chosen
Indicates that the recorded date of the most recent eruption is an estimate rather than an exact, precisely known date.
-
D.
lastEruptionStartDate
Indicates the date on which the most recent eruption of the entity began.
-
E.
youngestVolcanismLocation
Indicates the location where the most recent or youngest volcanic activity associated with an entity occurs or is observed.
- 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_69ca83d039f08190b9d10363221c69fb |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cdd0ca7f7c8190ba7ed37940aa933d |
completed | April 2, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9ed7e48190aa132ef8a69b49f9 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:03 p.m.