Triple
T17310882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IJlst |
E420289
|
entity |
| Predicate | distanceToSneek |
P126924
|
FINISHED |
| Object | about 3 km southwest |
—
|
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: about 3 km southwest | Statement: [IJlst, distanceToSneek, about 3 km southwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToSneek Context triple: [IJlst, distanceToSneek, about 3 km southwest]
-
A.
distancedFrom
Indicates that one entity is physically or metaphorically kept at a certain distance or separation from another entity.
-
B.
distanceToTheEntrance
Indicates the spatial distance between a given entity and the entrance of a specified place or structure.
-
C.
proximityToLandmark
Indicates a spatial relationship where one entity is located near or close to a specified landmark.
-
D.
distanceFromGoal
Indicates the measured or estimated separation between an entity’s current position and its intended goal or target state.
-
E.
distanceToSkegness
Indicates the measured or calculated spatial distance between a given entity and the location Skegness.
- 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_69d889d22b848190a4663d0b8f8f76e7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4399837b08190b7cf74201b3cb013 |
completed | April 19, 2026, 2:10 a.m. |
| PD | Predicate disambiguation | batch_69e3b01b9d1c8190a406dd941c9b11a1 |
completed | April 18, 2026, 4:23 p.m. |
| PDg | Predicate description generation | batch_69e3b2a225b08190a50f984caa6513b9 |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:43 a.m.