Triple
T24366657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yasur Volcano |
E614211
|
entity |
| Predicate | firstEuropeanObservationYear |
P14790
|
FINISHED |
| Object | 1774 |
—
|
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: 1774 | Statement: [Yasur Volcano, firstEuropeanObservationYear, 1774]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstEuropeanObservationYear Context triple: [Yasur Volcano, firstEuropeanObservationYear, 1774]
-
A.
wasFirstObservedIn
Indicates that an entity was initially noticed, recorded, or detected at a particular time or place.
-
B.
firstReportedYear
chosen
Indicates the year in which something was initially reported, documented, or made known for the first time.
-
C.
firstWidelyObserved
Indicates that something was initially noticed or recorded by a large number of observers or across a broad context for the first time.
-
D.
firstEuroAppearanceYear
Indicates the calendar year in which an entity made its first appearance or participation in a European competition or event.
-
E.
firstFireYear
Indicates the year in which a given location or entity first experienced a recorded fire event.
- 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_69e2d7dfe7f08190b7a1f3a36483ab05 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2938809f081908abf33edb62ed7f8 |
completed | April 29, 2026, 11:26 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:01 a.m.