Triple
T24656390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emerald Cave |
E610402
|
entity |
| Predicate | accessTunnelType |
P29550
|
FINISHED |
| Object | narrow sea tunnel |
—
|
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: narrow sea tunnel | Statement: [Emerald Cave, accessTunnelType, narrow sea tunnel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessTunnelType Context triple: [Emerald Cave, accessTunnelType, narrow sea tunnel]
-
A.
tunnelType
chosen
Indicates the specific kind or classification of a tunnel associated with an entity.
-
B.
usesTunnel
Indicates that one entity makes use of a tunnel as a passage or route to reach or connect to another entity.
-
C.
tunnelAllows
Indicates that a tunnel provides a passage or route that permits movement, access, or flow between two locations or entities.
-
D.
typeOfAccess
Indicates the specific kind or level of access that one entity has to another (such as read, write, or execute permissions).
-
E.
tunnelUse
Indicates that one entity makes use of or passes through a tunnel associated with another entity.
- 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_69e2c4d453248190a020354e93ef6282 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f41011d8048190be70329ba0bfb7c7 |
completed | May 1, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f40ed9d47881909fcfc0d04e8d074a |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 2:34 a.m.