Triple
T31054139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boris Stürmer |
E791348
|
entity |
| Predicate | sharesBorderWithConceptually |
P197903
|
FINISHED |
| Object | 1917 Russian revolutions |
—
|
NE NERFINISHED |
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: 1917 Russian revolutions | Statement: [Boris Stürmer, sharesBorderWithConceptually, 1917 Russian revolutions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesBorderWithConceptually Context triple: [Boris Stürmer, sharesBorderWithConceptually, 1917 Russian revolutions]
-
A.
shareBorderBetween
Indicates that two geographic or political entities have a common boundary where their territories directly touch.
-
B.
relatedBorder
Indicates that two geographic or political entities share a common boundary or border with each other.
-
C.
sharesBorderWithSector
Indicates that one sector directly touches and has a common boundary line with another sector.
-
D.
sharesBorderingNetworkWith
Indicates that two entities are connected through adjacent or directly neighboring positions within the same network structure.
-
E.
sharesBorderWithDepartment
Indicates that one administrative department directly borders or touches the territorial boundary of another department.
- 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_69f224cb08908190ba71ad9aa87518ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69feb8e856d48190aa34ad8ee8376e1c |
completed | May 9, 2026, 4:32 a.m. |
| PD | Predicate disambiguation | batch_69feb82a2b6c8190a473cc25976897be |
completed | May 9, 2026, 4:29 a.m. |
| PDg | Predicate description generation | batch_69feb8e6ed7881908446745c89c30784 |
completed | May 9, 2026, 4:32 a.m. |
Created at: April 29, 2026, 9 p.m.