Triple
T37699962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rock of Gibraltar |
E939030
|
entity |
| Predicate | hasTunnelNetwork |
P21069
|
FINISHED |
| Object | extensive military tunnels |
—
|
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: extensive military tunnels | Statement: [Rock of Gibraltar, hasTunnelNetwork, extensive military tunnels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTunnelNetwork Context triple: [Rock of Gibraltar, hasTunnelNetwork, extensive military tunnels]
-
A.
hasTunnel
chosen
Indicates that one entity possesses, contains, or is connected by a tunnel to another 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.
hasTunnelFunction
Indicates that one entity serves as a tunnel or provides a tunneling function for 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.
hasDuplexTunnel
Indicates that there exists a bidirectional (two-way) tunnel connection between two entities.
- 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_69f76eda6ae48190b3111071eeacc038 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.