Triple
T27861158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tutshill, Gloucestershire |
E704232
|
entity |
| Predicate | crossBorderLinksVia |
P105151
|
FINISHED |
| Object | Chepstow |
—
|
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: Chepstow | Statement: [Tutshill, Gloucestershire, crossBorderLinksVia, Chepstow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossBorderLinksVia Context triple: [Tutshill, Gloucestershire, crossBorderLinksVia, Chepstow]
-
A.
crossBorderLinks
chosen
Indicates connections or interactions that extend across or link entities in different geographic or political jurisdictions.
-
B.
crossBorderNode
Indicates a connection or element that spans or links entities across a defined boundary or border.
-
C.
crossBorderGatewayFor
Indicates that one entity functions as a gateway enabling traffic or interaction to cross a border or boundary for another entity.
-
D.
crossBorderRegion
Indicates a region that spans or intersects the boundary between two or more distinct territorial or jurisdictional areas.
-
E.
crossBorderPartner
Indicates a partnership relationship between entities that operate across national or jurisdictional borders.
- 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_69ef840f12408190b539d00d79658abf |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 27, 2026, 6:18 p.m.