Triple
T25144768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queens Road tram stop |
E629902
|
entity |
| Predicate | carParkOperator |
P49833
|
FINISHED |
| Object | Metrolink |
—
|
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: Metrolink | Statement: [Queens Road tram stop, carParkOperator, Metrolink]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carParkOperator Context triple: [Queens Road tram stop, carParkOperator, Metrolink]
-
A.
hasStationCarParkOperator
chosen
Indicates that a particular station’s car park is operated or managed by a specified operator.
-
B.
parkSystem
Indicates a relationship where an entity is part of, managed by, or associated with an organized system of parks or protected recreational areas.
-
C.
hasParkOperator
Indicates that a park is operated or managed by a specific organization or individual.
-
D.
parkServed
Indicates that a particular park is provided with services or coverage by a specified entity (such as a transit line, facility, or administrative body).
-
E.
servicePark
Indicates that one entity serves as a designated area or facility where vehicles or equipment are parked, maintained, or serviced in relation to another entity.
- 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_69e2ff349e408190a6f4a5a66279f54d |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f4684b30a8819088fb9f78020c3e1a |
completed | May 1, 2026, 8:46 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:29 a.m.