Triple
T26504188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volcano, Hawaii |
E669499
|
entity |
| Predicate | nearEntranceOf |
P115067
|
FINISHED |
| Object | Hawaiʻi Volcanoes National Park |
—
|
NE NERFINISHED |
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: Hawaiʻi Volcanoes National Park | Statement: [Volcano, Hawaii, nearEntranceOf, Hawaiʻi Volcanoes National Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearEntranceOf Context triple: [Volcano, Hawaii, nearEntranceOf, Hawaiʻi Volcanoes National Park]
-
A.
nearestEntrance
Indicates that one entrance is the closest access point to a given location or entity compared to all other possible entrances.
-
B.
hasEntranceOn
Indicates that one entity’s entrance or access point is located on or faces a specified side, boundary, or feature of another entity.
-
C.
hasLandmarkAtEntrance
Indicates that a specific landmark is located at or directly adjacent to the entrance of something.
-
D.
hasEntrance
Indicates that one entity possesses or provides an entry point or access way to another entity or space.
-
E.
distanceToTheEntrance
chosen
Indicates the spatial distance between a given entity and the entrance of a specified place or structure.
- 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_69eeb319ec70819090834c2591cf5f1e |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 1:15 a.m.