Triple
T260044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian Empire |
E5520
|
entity |
| Predicate | greatPower |
P404
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Russian Empire, greatPower, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: greatPower Context triple: [Russian Empire, greatPower, 19th century]
-
A.
majorPowerIn
chosen
Indicates that an entity holds significant political, economic, or military influence within a specified domain, region, or context.
-
B.
mainAlliedPower
Indicates that an entity serves as a primary or leading ally to another entity within an alliance or coalition.
-
C.
notableAlliedNation
Indicates that one nation is prominently recognized as an ally or key partner of another nation.
-
D.
geopoliticalRole
Indicates the specific political or strategic function, status, or position an entity holds within or among geopolitical units such as states, regions, or international organizations.
-
E.
isNATOAllyOf
Indicates that one entity is a member of NATO and has a formal alliance relationship with the other entity within the NATO framework.
- 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_69a2580a64ac8190ad76e34bb0715b5e |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25f921c2881908821ca2c03815eae |
completed | Feb. 28, 2026, 3:22 a.m. |
| PD | Predicate disambiguation | batch_69a25b6b3ea88190bbd858999e42efae |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:55 a.m.