Triple
T25161438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Order |
E626449
|
entity |
| Predicate | NasakomExpandsTo |
P14356
|
FINISHED |
| Object | nationalism, religion, communism |
—
|
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: nationalism, religion, communism | Statement: [Old Order, NasakomExpandsTo, nationalism, religion, communism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NasakomExpandsTo Context triple: [Old Order, NasakomExpandsTo, nationalism, religion, communism]
-
A.
sectorExpansion
Indicates an increase or broadening in the size, scope, or activity level of a particular sector or industry over time.
-
B.
formerUSExpansion
Indicates that an entity previously expanded into or operated within the United States but no longer does so.
-
C.
expands
chosen
Indicates that one entity increases in size, volume, scope, or extent relative to a previous state or another entity.
-
D.
expansionRegion
Indicates a region or area into which something (such as a structure, process, or influence) is intended or allowed to expand.
-
E.
expandedTerritoryTo
Indicates that one entity has increased the geographic area under its control or influence to include the territory of 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_69e2ff2834ec8190b0872e2ec3d76023 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f46b8d45548190a5bdb4fba1d3ba4e |
completed | May 1, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:31 a.m.