Triple
T28907332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ambrosden |
E733118
|
entity |
| Predicate | distanceToBicester_miles |
P54627
|
FINISHED |
| Object | approximately 3 |
—
|
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 3 | Statement: [Ambrosden, distanceToBicester_miles, approximately 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToBicester_miles Context triple: [Ambrosden, distanceToBicester_miles, approximately 3]
-
A.
distanceToBicester
chosen
Indicates the spatial distance between a given entity and the location of Bicester.
-
B.
distanceToCirencester
Indicates the spatial distance between a given entity’s location and the town of Cirencester.
-
C.
distanceToBasingstoke
Indicates the spatial distance between a given entity and the location of Basingstoke.
-
D.
distanceToLeicester
Indicates the spatial distance between a given entity’s location and the location of Leicester.
-
E.
distanceToChichester
Indicates the measured distance between a given location or entity and the place Chichester.
- 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_69f05b096d208190958a57d2e4b5a93a |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_6a00512437d48190ad20324968ead5f4 |
completed | May 10, 2026, 9:34 a.m. |
| PD | Predicate disambiguation | batch_6a0050227350819099f41369c3d168be |
completed | May 10, 2026, 9:30 a.m. |
Created at: April 28, 2026, 8:08 a.m.