Triple
T29118306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Advance Doctrine |
E737106
|
entity |
| Predicate | advocatedDirectionOfExpansion |
P64848
|
FINISHED |
| Object | Siberia |
—
|
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: Siberia | Statement: [Northern Advance Doctrine, advocatedDirectionOfExpansion, Siberia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: advocatedDirectionOfExpansion Context triple: [Northern Advance Doctrine, advocatedDirectionOfExpansion, Siberia]
-
A.
territorialExpansionDirection
chosen
Indicates the primary geographic direction in which an entity’s territory is expanding or has expanded.
-
B.
sectorExpansion
Indicates an increase or broadening in the size, scope, or activity level of a particular sector or industry over time.
-
C.
plannedExpansion
Indicates that an entity has a scheduled or intended increase in size, capacity, scope, or presence in the future.
-
D.
plannedExtensionDirection
Indicates the intended directional path or orientation along which something is planned to be extended in the future.
-
E.
expands
Indicates that one entity increases in size, volume, scope, or extent relative to a previous state or another entity.
- F. None of above.
Provenance (3 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_69f077ed54e08190bb02a744e8121a66 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f661f244fc8190b931f5099dc432d2 |
completed | May 2, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 11:23 a.m.