Triple
T839376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port Talbot |
E18141
|
entity |
| Predicate | distanceToSwansea_km |
P17622
|
FINISHED |
| Object | approximately 11 |
—
|
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: approximately 11 | Statement: [Port Talbot, distanceToSwansea_km, approximately 11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToSwansea_km Context triple: [Port Talbot, distanceToSwansea_km, approximately 11]
-
A.
distanceToSwansea
chosen
Indicates the spatial distance between a given entity’s location and the location of Swansea.
-
B.
distanceToLondon
Indicates the measured distance between a given entity’s location and the city of London.
-
C.
distanceToCardiff
Indicates the spatial distance between a given entity’s location and the city of Cardiff.
-
D.
distanceFromCentralLondon
Indicates the spatial separation or length of travel between a given location and central London.
-
E.
distanceFromGlasgow
Indicates the spatial distance separating a given entity or location from Glasgow.
- 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_69a49389f44881909a608fb27d89f247 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4abe4ab1081909207ae2eec1898d9 |
completed | March 1, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69a4aa7dfc5c8190890c9df485d73a86 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.