Triple
T24219781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HBY |
E601414
|
entity |
| Predicate | lineOfStationIdentified |
P96283
|
FINISHED |
| Object | Piccadilly line |
—
|
NE NERFINISHED |
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: Piccadilly line | Statement: [HBY, lineOfStationIdentified, Piccadilly line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineOfStationIdentified Context triple: [HBY, lineOfStationIdentified, Piccadilly line]
-
A.
identifiesStationWithinLine
Indicates that a specific station is recognized as belonging to, or located within, a particular transit line.
-
B.
stationOnLine
chosen
Indicates that a particular station is located on or served by a specific transit line.
-
C.
stationNumber
Indicates the specific station identifier or code assigned to an entity within a system or network.
-
D.
lineServed
Indicates that a particular transportation line (such as a bus, train, or metro line) provides service to or is operated at a given stop, station, or route segment.
-
E.
hasAdjacentStationOnLine 5
Indicates that one station is directly next to another station along line 5, with no other stations in between on that line.
- 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_69e29537ca548190b94a37ebe1977caf |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f2820cdd3c8190998d6d901224c09f |
completed | April 29, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:59 p.m.