Triple
T22046271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gurudongmar Lake |
E544769
|
entity |
| Predicate | distanceFromLachen |
P146380
|
FINISHED |
| Object | about 65 kilometers by road |
—
|
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 65 kilometers by road | Statement: [Gurudongmar Lake, distanceFromLachen, about 65 kilometers by road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromLachen Context triple: [Gurudongmar Lake, distanceFromLachen, about 65 kilometers by road]
-
A.
distanceFromLachung
Indicates the spatial distance between an entity and the location Lachung.
-
B.
distanceToLucerne
Indicates the spatial distance between an entity and the location Lucerne.
-
C.
distanceFromPaihia
Indicates the distance between a given place or object and the location Paihia.
-
D.
distanceFromZermatt
Indicates the spatial distance between an entity and the location Zermatt.
-
E.
distanceToLausanne
Indicates the measured distance between a given entity’s location and the city of Lausanne.
- 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_69e11e32445c8190ab97089b48a130bb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1282f4a448190bca55348c457a4bd |
completed | April 28, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69e6f643ca74819083e8ab78e843f243 |
completed | April 21, 2026, 4 a.m. |
| PDg | Predicate description generation | batch_69e6fad4a540819096cdd5ea08527220 |
completed | April 21, 2026, 4:19 a.m. |
Created at: April 16, 2026, 8:26 p.m.