Triple
T26320582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balmullo |
E662096
|
entity |
| Predicate | distanceToStAndrews_km |
P195891
|
FINISHED |
| Object | approximately 10 |
—
|
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 10 | Statement: [Balmullo, distanceToStAndrews_km, approximately 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToStAndrews_km Context triple: [Balmullo, distanceToStAndrews_km, approximately 10]
-
A.
distanceToEdinburgh_km
Indicates the physical distance, measured in kilometers, between an entity’s location and Edinburgh.
-
B.
distanceToAyr
Indicates the measured distance between a given entity or location and Ayr.
-
C.
distanceFromStirling
Indicates the spatial distance measured from the reference location Stirling to another place or entity.
-
D.
distanceToKirkwall
Indicates the spatial distance between a given location and the location of Kirkwall.
-
E.
distanceFromGlasgow
Indicates the spatial distance separating a given entity or location from Glasgow.
- F. None of above. chosen
Provenance (4 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_69ee812e73048190aae587f1d51e5a06 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69fdee770af48190aca2670db50f8b49 |
completed | May 8, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69fdecec98a08190a357d816dc2a6dbe |
completed | May 8, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69fdee75d1408190bba58a9cef200a54 |
completed | May 8, 2026, 2:08 p.m. |
Created at: April 26, 2026, 10:28 p.m.