Triple
T4789958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ropsha |
E106576
|
entity |
| Predicate | distanceFromSaintPetersburg |
P58440
|
FINISHED |
| Object | approximately 30–40 kilometers |
—
|
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 30–40 kilometers | Statement: [Ropsha, distanceFromSaintPetersburg, approximately 30–40 kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromSaintPetersburg Context triple: [Ropsha, distanceFromSaintPetersburg, approximately 30–40 kilometers]
-
A.
distanceFromMoscow_km
Indicates the physical distance, measured in kilometers, between a given entity’s location and Moscow.
-
B.
railDistanceFromMoscowCenter_km
Indicates the distance in kilometers from the center of Moscow to a location when traveling by rail.
-
C.
distanceToArkhangelskApproxKm
Indicates the approximate distance, measured in kilometers, between a given entity’s location and Arkhangelsk.
-
D.
distanceToYakutsk
Indicates the spatial distance between a given entity and the location of Yakutsk.
-
E.
distanceToHelsinki_km
Indicates the physical distance, measured in kilometers, between an entity’s location and the city of Helsinki.
- 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_69bd43f4a9588190bf73e20bc27c03cc |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd65dce6888190a0b1bdf416fb62b9 |
completed | March 20, 2026, 3:21 p.m. |
| PD | Predicate disambiguation | batch_69bd622e1b408190806c15c61519fc74 |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd631328fc81909b28ae0a2a3ed9bb |
completed | March 20, 2026, 3:09 p.m. |
Created at: March 20, 2026, 1:22 p.m.