Triple
T11051753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salekhard |
E261270
|
entity |
| Predicate | distanceToYamalPeninsula |
P97520
|
FINISHED |
| Object | near southern end of Yamal Peninsula |
—
|
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: near southern end of Yamal Peninsula | Statement: [Salekhard, distanceToYamalPeninsula, near southern end of Yamal Peninsula]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToYamalPeninsula Context triple: [Salekhard, distanceToYamalPeninsula, near southern end of Yamal Peninsula]
-
A.
distanceToYakutsk
Indicates the spatial distance between a given entity and the location of Yakutsk.
-
B.
distanceToPetropavlovskKamchatsky
Indicates the spatial distance between an entity and the location of Petropavlovsk-Kamchatsky.
-
C.
distanceToArkhangelskApproxKm
Indicates the approximate distance, measured in kilometers, between a given entity’s location and Arkhangelsk.
-
D.
distanceToAlaskaApproxKm
Indicates the approximate distance, measured in kilometers, between a given entity’s location and the state of Alaska.
-
E.
distanceTo_Vostok 5_minimum
Indicates that the minimum distance between an entity and Vostok 5 is being specified or constrained.
- 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d798698bd88190aa97afd37f55e19f |
completed | April 9, 2026, 12:15 p.m. |
| PD | Predicate disambiguation | batch_69d7440da46c8190a77380d5d747ac9c |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750c99f9881908ee2b01b6ce4b3a1 |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:26 p.m.