Triple
T27844411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volcano Art Center |
E703775
|
entity |
| Predicate | operatesNear |
P196388
|
FINISHED |
| Object | Kīlauea volcano |
—
|
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: Kīlauea volcano | Statement: [Volcano Art Center, operatesNear, Kīlauea volcano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesNear Context triple: [Volcano Art Center, operatesNear, Kīlauea volcano]
-
A.
operatedNear
Indicates that one entity performed an operation or activity in close physical proximity to another entity.
-
B.
nearbyUse
Indicates that one entity uses or operates another entity that is located nearby or in close physical proximity.
-
C.
locatedNearPass
Indicates that one entity is situated close to a mountain pass or similar passageway.
-
D.
operatedFacilityNear
Indicates that an entity operated a facility located in close geographic proximity to another specified entity or place.
-
E.
hasNearbyFacility
Indicates that one entity is located close to or in the vicinity of a particular facility.
- 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_69ef840d9e3c819093615ebff4ec22be |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fe30bc64308190b603ff1b30c2aeee |
completed | May 8, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fe2f7175b081908dd61e1513620bbe |
completed | May 8, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69fe30bb07d08190877539d5aa202d24 |
completed | May 8, 2026, 6:51 p.m. |
Created at: April 27, 2026, 6:05 p.m.