Triple
T7370609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aylsham |
E169990
|
entity |
| Predicate | distanceToNorwich_km |
P4778
|
FINISHED |
| Object | approximately 15 |
—
|
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 15 | Statement: [Aylsham, distanceToNorwich_km, approximately 15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToNorwich_km Context triple: [Aylsham, distanceToNorwich_km, approximately 15]
-
A.
distanceFromNorwich
chosen
Indicates the measured distance between a given place or object and the location of Norwich.
-
B.
distanceToSunderland_km
Indicates the physical distance, measured in kilometers, between a given place and Sunderland.
-
C.
distanceToSwaffham
Indicates the spatial distance between a given entity and the location Swaffham.
-
D.
distanceToLerwickKilometers
Indicates the physical distance, measured in kilometers, between a given entity’s location and the town of Lerwick.
-
E.
distanceToWymondham
Indicates the spatial distance between a given entity or location and Wymondham.
- 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_69c68a5bfaac81909ce7f001dfb70c76 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f182df5c81908964fbaa3f8ec790 |
completed | March 27, 2026, 9:07 p.m. |
| PD | Predicate disambiguation | batch_69c6f02ee3e08190a7a00c981129b22c |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:07 p.m.