Triple
T2552516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stonehenge |
E56657
|
entity |
| Predicate | distanceFromSalisbury |
P40797
|
FINISHED |
| Object | about 13 km north |
—
|
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: about 13 km north | Statement: [Stonehenge, distanceFromSalisbury, about 13 km north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromSalisbury Context triple: [Stonehenge, distanceFromSalisbury, about 13 km north]
-
A.
distanceToSwaffham
Indicates the spatial distance between a given entity and the location Swaffham.
-
B.
distanceToCarlisle
Indicates the spatial distance between a given entity or location and Carlisle.
-
C.
distanceFromHuntingdon
Indicates the spatial distance between a given entity and the location of Huntingdon.
-
D.
distanceToCanterbury
Indicates the spatial distance between a given entity’s location and the location of Canterbury.
-
E.
distanceFromDover
Indicates the measured distance between a given entity or location and the place named Dover.
- 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_69ab4a4bfec081908039988ec4c86e28 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd5a33234819082ad49fa6594b6be |
completed | March 7, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69abd0c8b6f08190a68645db3e8b779a |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd5a1cd508190a660b9a3c6b7cbcb |
completed | March 7, 2026, 7:37 a.m. |
Created at: March 6, 2026, 9:48 p.m.