Triple
T24977708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phoenix Park park and ride |
E625070
|
entity |
| Predicate | operatorRelation |
P152818
|
FINISHED |
| Object | served by Nottingham Express Transit trams |
—
|
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: served by Nottingham Express Transit trams | Statement: [Phoenix Park park and ride, operatorRelation, served by Nottingham Express Transit trams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorRelation Context triple: [Phoenix Park park and ride, operatorRelation, served by Nottingham Express Transit trams]
-
A.
subjectRelation
Indicates that one entity stands in a specified relational role or connection to another entity.
-
B.
relatesOperator
chosen
Indicates that one entity is associated with, or functions as, an operator in relation to another entity.
-
C.
valueRelation
Indicates a comparative or associative relationship between the values or magnitudes of two or more entities.
-
D.
allyRelation
Indicates a cooperative, supportive relationship in which the entities act as allies toward shared or aligned goals.
-
E.
ownershipRelation
Indicates that one entity possesses legal or recognized ownership rights over 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_69e2ff254570819093d197b1900305ac |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 18, 2026, 6:02 a.m.