Triple
T14750790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ussuriysk |
E346595
|
entity |
| Predicate | distanceToVladivostok_km |
P115642
|
FINISHED |
| Object | about 100 |
—
|
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 100 | Statement: [Ussuriysk, distanceToVladivostok_km, about 100]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToVladivostok_km Context triple: [Ussuriysk, distanceToVladivostok_km, about 100]
-
A.
distanceToPetropavlovskKamchatsky
Indicates the spatial distance between an entity and the location of Petropavlovsk-Kamchatsky.
-
B.
distanceFromMoscow_km
Indicates the physical distance, measured in kilometers, between a given entity’s location and Moscow.
-
C.
distanceToArkhangelskApproxKm
Indicates the approximate distance, measured in kilometers, between a given entity’s location and Arkhangelsk.
-
D.
distanceToVladikavkaz
Indicates the spatial distance between a given entity and the city of Vladikavkaz.
-
E.
distanceToAstrakhan
Indicates the measured or specified distance between a given entity and the location of Astrakhan.
- 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_69d822e6f1c88190bc494d491a907114 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7d2e1748190b16ede681fe52872 |
completed | April 14, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69de8bf9331481909582045cd567d91f |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de8f4b67cc8190b84b59fcec5cf579 |
completed | April 14, 2026, 7:02 p.m. |
Created at: April 10, 2026, 1:30 a.m.