Triple
T8354610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Ontake |
E196652
|
entity |
| Predicate | hasObservationPoints |
P50321
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Mount Ontake, hasObservationPoints, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasObservationPoints Context triple: [Mount Ontake, hasObservationPoints, yes]
-
A.
hasObservationSite
Indicates that something (such as a measurement, event, or observation activity) is associated with or took place at a specific observation site or location.
-
B.
hasObservationArea
chosen
Indicates that an entity possesses or includes a designated area from which observations or monitoring activities are conducted.
-
C.
hasObservation
Indicates that an entity records, contains, or is associated with a specific observation or measured instance.
-
D.
hasObservationFacility
Indicates that an entity possesses or is associated with a facility used for observing, monitoring, or collecting data about something.
-
E.
hasObservationMethod
Indicates that a particular method, technique, or procedure is used to perform or obtain an observation.
- 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_69ca82f08b348190bfb7881944bbff6f |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb8048edb88190a1980ad74818b898 |
completed | March 31, 2026, 8:05 a.m. |
| PD | Predicate disambiguation | batch_69cb70ca25548190b0f90c5384e3fb3c |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:59 p.m.