Triple
T11552691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Butlers Lane railway station |
E273934
|
entity |
| Predicate | hasCarParkOperator |
P49833
|
FINISHED |
| Object | railway operator-managed car park |
—
|
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: railway operator-managed car park | Statement: [Butlers Lane railway station, hasCarParkOperator, railway operator-managed car park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCarParkOperator Context triple: [Butlers Lane railway station, hasCarParkOperator, railway operator-managed car park]
-
A.
hasStationCarParkOperator
chosen
Indicates that a particular station’s car park is operated or managed by a specified operator.
-
B.
hasParkOperator
Indicates that a park is operated or managed by a specific organization or individual.
-
C.
hasParkingLotOwner
Indicates that a parking lot is owned or possessed by a specific owner.
-
D.
hasParkOwner
Indicates that an entity serves as the owner or legal controller of a particular park.
-
E.
hasParkingFor
Indicates that a place or facility provides designated parking spaces suitable for a specified type of vehicle or user.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d88a85b9ac8190a57c1fdaeacbe3d6 |
completed | April 10, 2026, 5:28 a.m. |
| PD | Predicate disambiguation | batch_69d8087e57b48190a4c253dc0210f9d4 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.