Triple
T28342110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Highgate Underground Station |
E717840
|
entity |
| Predicate | hasDisusedTunnels |
P137701
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Highgate Underground Station, hasDisusedTunnels, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDisusedTunnels Context triple: [Highgate Underground Station, hasDisusedTunnels, true]
-
A.
numberOfTunnels
Indicates the quantity of tunnels associated with or passing through a given entity or location.
-
B.
hasTunnel
Indicates that one entity possesses, contains, or is connected by a tunnel to another entity.
-
C.
hasTunnelSections
Indicates that an entity includes or is composed of multiple distinct tunnel segments or portions.
-
D.
tunnelsStatus
chosen
Indicates the current operational or physical condition of tunnels, such as whether they are open, closed, or otherwise restricted.
-
E.
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.
- 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_69eff6eb30388190b898b96c4be6f49d |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: April 28, 2026, 12:40 a.m.