Triple
T26647944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kirkøy |
E668969
|
entity |
| Predicate | hasTunnelConnectionTo |
P21069
|
FINISHED |
| Object | Asmaløy |
—
|
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: Asmaløy | Statement: [Kirkøy, hasTunnelConnectionTo, Asmaløy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTunnelConnectionTo Context triple: [Kirkøy, hasTunnelConnectionTo, Asmaløy]
-
A.
hasTunnel
chosen
Indicates that one entity possesses, contains, or is connected by a tunnel to another entity.
-
B.
hasTunnelFunction
Indicates that one entity serves as a tunnel or provides a tunneling function for another entity.
-
C.
hasServiceTunnel
Indicates that one entity is connected to or accessed via a dedicated service tunnel associated with another entity.
-
D.
hasEmergencyTunnel
Indicates that one location, structure, or system possesses a dedicated emergency tunnel connecting it to another place or route for use in urgent or hazardous situations.
-
E.
hasTunnelShape
Indicates that something possesses a form or configuration resembling a tunnel, typically elongated, enclosed, and passage-like.
- 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_69ee9d00eb5481908d6c6d0ada2f0c9a |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f616778678819095bc601b19dbe0bd |
completed | May 2, 2026, 3:21 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 2:32 a.m.