Triple
T34828598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manorbier railway station |
E1004000
|
entity |
| Predicate | nearbyAuthority |
P12057
|
FINISHED |
| Object | Pembrokeshire County Council |
—
|
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: Pembrokeshire County Council | Statement: [Manorbier railway station, nearbyAuthority, Pembrokeshire County Council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyAuthority Context triple: [Manorbier railway station, nearbyAuthority, Pembrokeshire County Council]
-
A.
nearbyPoliticalEntity
Indicates that one political entity is geographically close to another political entity, without necessarily sharing a border.
-
B.
governingBodyNearby
chosen
Indicates that a governing body is located in close physical proximity to the referenced entity or area.
-
C.
servesAsMunicipalAuthorityFor
Indicates that an entity functions as the official municipal governing or administrative authority for a specified locality or jurisdiction.
-
D.
nearbyTo
Indicates that one entity is located close in distance or position to another entity.
-
E.
hasNearbyJurisdiction
Indicates that one jurisdiction is geographically close to or adjacent to another jurisdiction.
- 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_69f76db7d1b4819093bd4912d80d845d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe87b609888190913b0c3f787ecdba |
completed | May 9, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69fe8731af48819092084f6f74bf052d |
completed | May 9, 2026, 1 a.m. |
Created at: May 3, 2026, 4 p.m.