Triple
T36414142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bow Road Underground station |
E896958
|
entity |
| Predicate | hasPayphones |
P201595
|
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: [Bow Road Underground station, hasPayphones, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPayphones Context triple: [Bow Road Underground station, hasPayphones, true]
-
A.
hasCommunicationTowers
Indicates that one entity possesses, contains, or is equipped with communication towers used for transmitting or receiving signals.
-
B.
hasTelephoneService
Indicates that a subject is provided with or connected to telephone service.
-
C.
hasSatelliteTerminal
Indicates that an entity is equipped with or connected to a satellite communication terminal.
-
D.
hasCallCenter
Indicates that an entity operates, is associated with, or is served by a call center.
-
E.
hasStations
Indicates that one entity possesses, contains, or is associated with one or more stations.
- F. None of above. chosen
Provenance (4 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_69f76e54ce408190849acc3f7758937c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a000a1d8fa88190a1d82ac746565c48 |
completed | May 10, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_6a0008b26eb88190ae03b2309a614774 |
completed | May 10, 2026, 4:25 a.m. |
| PDg | Predicate description generation | batch_6a000a1c8f8881908293ab4f7207d25f |
completed | May 10, 2026, 4:31 a.m. |
Created at: May 3, 2026, 4:10 p.m.