Triple
T24656744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kevelaer |
E610413
|
entity |
| Predicate | distanceToGoch |
P157665
|
FINISHED |
| Object | approximately 10 km east |
—
|
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 10 km east | Statement: [Kevelaer, distanceToGoch, approximately 10 km east]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToGoch Context triple: [Kevelaer, distanceToGoch, approximately 10 km east]
-
A.
distanceToGoole
Indicates the spatial distance between an entity and the location named Goole.
-
B.
distanceFromGwangju
Indicates the spatial distance between a given location and the city of Gwangju.
-
C.
distanceFromGori
Indicates the spatial distance between a given entity or location and the place named Gori.
-
D.
distanceToSeoul
Indicates the measured or estimated spatial distance between a given entity’s location and the city of Seoul.
-
E.
distanceFromHo
Indicates the spatial distance measured from a specified reference point or origin labeled "Ho" to another entity.
- 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_69e2c4d453248190a020354e93ef6282 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442a977b08190b44eac040cb90211 |
completed | May 1, 2026, 6:05 a.m. |
| PDg | Predicate description generation | batch_69f44a3adb7c8190941572f718b3b93c |
completed | May 1, 2026, 6:37 a.m. |
Created at: April 18, 2026, 2:34 a.m.