Triple
T4866039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charing Cross Underground station |
E108771
|
entity |
| Predicate | hasNightTubeService |
P48928
|
FINISHED |
| Object | yes (on some lines and nights) |
—
|
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: yes (on some lines and nights) | Statement: [Charing Cross Underground station, hasNightTubeService, yes (on some lines and nights)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNightTubeService Context triple: [Charing Cross Underground station, hasNightTubeService, yes (on some lines and nights)]
-
A.
hasNightTubeServiceOn
chosen
Indicates that a transport service operates Night Tube (overnight) service on the specified day or line.
-
B.
hasTube
Indicates that one entity possesses, includes, or is equipped with a tube as a component or feature.
-
C.
isIlluminatedAtNight
Indicates that an entity receives or emits sufficient light to be visibly illuminated during nighttime conditions.
-
D.
hasMediaHub
Indicates that one entity possesses, contains, or is associated with a central platform or facility for managing, distributing, or accessing media content.
-
E.
nightService
Indicates that a service operates or is available during nighttime hours.
- 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_69bd440b965081908b0557721cae6338 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6d7a42f88190bb1ef7261bcbc2a8 |
completed | March 20, 2026, 3:53 p.m. |
| PD | Predicate disambiguation | batch_69bd6c27334481909ba8ac80854f7d8e |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:26 p.m.