Triple
T31025175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Habu missions |
E790548
|
entity |
| Predicate | targetRegions |
P110234
|
FINISHED |
| Object | Soviet Far East |
—
|
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: Soviet Far East | Statement: [Habu missions, targetRegions, Soviet Far East]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetRegions Context triple: [Habu missions, targetRegions, Soviet Far East]
-
A.
includedRegions
Indicates that certain regions are contained within, or form part of, a larger specified region or set of regions.
-
B.
typicalTargetRegion
chosen
Indicates the region or area that an action, process, or effect is most commonly directed toward or occurs in.
-
C.
exportRegion
Indicates the region or geographic area from which goods, services, or resources are exported.
-
D.
coreRegionOf
Indicates that one entity constitutes the central or most essential part of another entity’s structure, area, or domain.
-
E.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
- 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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
Created at: April 29, 2026, 8:58 p.m.