Triple
T34716469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annan |
E1000783
|
entity |
| Predicate | hasDistanceToEnglishBorder |
P73340
|
FINISHED |
| Object | approximately 8 miles |
—
|
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 8 miles | Statement: [Annan, hasDistanceToEnglishBorder, approximately 8 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDistanceToEnglishBorder Context triple: [Annan, hasDistanceToEnglishBorder, approximately 8 miles]
-
A.
distanceToEnglishBorder
chosen
Indicates the spatial distance between a given location and the border of England.
-
B.
hasBorderLengthWithUSA
Indicates that the length of the land or maritime border shared between a given country or region and the USA has a specified measurement.
-
C.
distanceToUSBorderByRoad_km
Indicates the distance in kilometers from a given location to the nearest point on the United States border when traveling by road.
-
D.
distanceToCanadianBorder
Indicates the measured or estimated spatial distance between a given location and the nearest point on the Canadian national border.
-
E.
distanceToSpanishBorder
Indicates the measured distance between a given location and the border of Spain.
- 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_69f76dad3f108190a280fd0a2f4ee89a |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ff1e3e13c08190bb8990c44716b746 |
completed | May 9, 2026, 11:45 a.m. |
| PD | Predicate disambiguation | batch_69ff1dfcaf2c8190aaf2b428d57b7782 |
completed | May 9, 2026, 11:43 a.m. |
Created at: May 3, 2026, 3:59 p.m.