Triple
T2012441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OVO Hydro |
E43716
|
entity |
| Predicate | parkingFacility |
P28595
|
FINISHED |
| Object | multi-storey 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: multi-storey car park | Statement: [OVO Hydro, parkingFacility, multi-storey car park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parkingFacility Context triple: [OVO Hydro, parkingFacility, multi-storey car park]
-
A.
parkingStructure
chosen
Indicates that one entity is a parking facility or structure associated with another entity (such as a building, location, or organization).
-
B.
parkingType
Indicates the specific kind or category of parking arrangement associated with an entity (e.g., street, garage, lot, reserved).
-
C.
parkSystem
Indicates a relationship where an entity is part of, managed by, or associated with an organized system of parks or protected recreational areas.
-
D.
hasParking
Indicates that a place or facility provides designated parking space(s) available for use.
-
E.
parkSection
Indicates a relationship where a specific area or subsection belongs to, is contained within, or is designated as part of a larger park.
- 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_69a88716e9f08190946313fdc949e3cf |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb8b2ed6c8190ad51f0af90db2a02 |
completed | March 7, 2026, 5:33 a.m. |
| PD | Predicate disambiguation | batch_69abb7a03a1c81909ad50d56667db2d5 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:37 p.m.