Triple
T16282096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nizhnekamsk |
E395290
|
entity |
| Predicate | distanceFromKazan |
P122509
|
FINISHED |
| Object | about 240 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: about 240 km east | Statement: [Nizhnekamsk, distanceFromKazan, about 240 km east]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromKazan Context triple: [Nizhnekamsk, distanceFromKazan, about 240 km east]
-
A.
distanceToGrozny_km
Indicates the physical distance, measured in kilometers, between a given location and the city of Grozny.
-
B.
distanceFromMoscow_km
Indicates the physical distance, measured in kilometers, between a given entity’s location and Moscow.
-
C.
distanceToAstrakhan
Indicates the measured or specified distance between a given entity and the location of Astrakhan.
-
D.
distanceToSaratov_km
Indicates the physical distance, measured in kilometers, between a given entity’s location and the city of Saratov.
-
E.
distanceFromSamarkand_km
Indicates the physical distance, measured in kilometers, between a given place or entity and the city of Samarkand.
- 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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e24910c6b881909ae5cc0908dd8eb2 |
completed | April 17, 2026, 2:52 p.m. |
| PD | Predicate disambiguation | batch_69e219f68d308190b71c1601303f0628 |
completed | April 17, 2026, 11:31 a.m. |
| PDg | Predicate description generation | batch_69e21e56e0348190a3d9475360231a70 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:05 a.m.