Triple
T5756197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle |
E126973
|
entity |
| Predicate | distanceToHastings |
P66200
|
FINISHED |
| Object | approximately 6 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 6 miles | Statement: [Battle, distanceToHastings, approximately 6 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToHastings Context triple: [Battle, distanceToHastings, approximately 6 miles]
-
A.
distanceToHunstanton
Indicates the measured spatial distance between a given entity and the location Hunstanton.
-
B.
distanceToHuddersfield
Indicates the spatial distance between a given entity or location and the town of Huddersfield.
-
C.
distanceToStAlbans
Indicates the measured distance between a given entity’s location and the location of St Albans.
-
D.
distanceFromHuntingdon
Indicates the spatial distance between a given entity and the location of Huntingdon.
-
E.
distanceToSwaffham
Indicates the spatial distance between a given entity and the location Swaffham.
- 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_69c00832aedc81909899801b141fa3b4 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02906848c8190bf7b0d62f57c27fa |
completed | March 22, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c021cc68648190bb86d049ebe80f12 |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c028fec2bc819083f5dca6a8d9d435 |
completed | March 22, 2026, 5:38 p.m. |
Created at: March 22, 2026, 3:49 p.m.