Triple
T30683623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Barn |
E781122
|
entity |
| Predicate | distanceToGravesend |
P203216
|
FINISHED |
| Object | approximately 4 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 4 miles | Statement: [New Barn, distanceToGravesend, approximately 4 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToGravesend Context triple: [New Barn, distanceToGravesend, approximately 4 miles]
-
A.
distanceToSouthend-on-Sea
Indicates the spatial distance between a given entity and the location Southend-on-Sea.
-
B.
distanceToBirkenhead
Indicates the spatial distance between a given entity and the location Birkenhead.
-
C.
distanceToFolkestone
Indicates the spatial distance between a given location or entity and the town of Folkestone.
-
D.
approxDistanceFromThames
Indicates that one entity is located at an approximate distance from the River Thames.
-
E.
distanceToSouthampton
Indicates the measured distance between a given entity’s location and the location of Southampton.
- 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a013d7180d08190b76f64cb430af9e1 |
completed | May 11, 2026, 2:22 a.m. |
| PD | Predicate disambiguation | batch_6a013c77d23c8190bb59e458b506d6e9 |
completed | May 11, 2026, 2:18 a.m. |
| PDg | Predicate description generation | batch_6a013d70e2448190a034e8a11a457008 |
completed | May 11, 2026, 2:22 a.m. |
Created at: April 29, 2026, 8:33 p.m.