Triple
T13548394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Ives Park and Ride |
E323574
|
entity |
| Predicate | ownerOrManager |
P13496
|
FINISHED |
| Object | local transport authority (Cambridgeshire area) |
—
|
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: local transport authority (Cambridgeshire area) | Statement: [St Ives Park and Ride, ownerOrManager, local transport authority (Cambridgeshire area)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownerOrManager Context triple: [St Ives Park and Ride, ownerOrManager, local transport authority (Cambridgeshire area)]
-
A.
ownerOrFounder
Indicates that an entity either owns or has founded another entity, capturing both ownership and founding relationships.
-
B.
ownsOrManages
chosen
Indicates that one entity has ownership of, or managerial control over, another entity.
-
C.
ownerRole
Indicates the role or capacity in which an entity serves as the owner of another entity.
-
D.
associatedWithManager
Indicates that an entity has a managerial connection or relationship with a specific manager.
-
E.
ownerInSeries
Indicates that an entity serves as the owner or controlling party within the context of a particular series or sequence.
- 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_69d8076776248190bdf0d4fa1f85a5fc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbbb9ee3f081909056dc1a92c40b7a |
completed | April 12, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69dbae13bec4819084c1770638c00ed9 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:45 p.m.