Triple
T26250107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rayne |
E656557
|
entity |
| Predicate | distanceToBraintree |
P195433
|
FINISHED |
| Object | approximately 2 miles west |
—
|
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 2 miles west | Statement: [Rayne, distanceToBraintree, approximately 2 miles west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToBraintree Context triple: [Rayne, distanceToBraintree, approximately 2 miles west]
-
A.
distanceToChippingNorton
Indicates the spatial distance between a given entity and the location of Chipping Norton.
-
B.
distanceToBray
Indicates the spatial distance between a given entity and the location named Bray.
-
C.
distanceToBawtry
Indicates the spatial distance between a given entity and the location of Bawtry.
-
D.
distanceToMoshi
Indicates the spatial distance between a given entity and the location Moshi.
-
E.
distanceToBingham
Indicates the measured or calculated distance between a given entity and the location named Bingham.
- 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_69ee5b4d25ac819086acb51184602576 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69fdd2be648c8190b60b3d1caeb44364 |
completed | May 8, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69fdd14a5c708190a6f95ec61f4fc28f |
completed | May 8, 2026, 12:04 p.m. |
| PDg | Predicate description generation | batch_69fdd2bda90881909aa229194d014ba7 |
completed | May 8, 2026, 12:10 p.m. |
Created at: April 26, 2026, 9:06 p.m.