Triple
T16136456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States |
E391540
|
entity |
| Predicate | isMajorMilitaryPower |
P404
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [United States, isMajorMilitaryPower, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorMilitaryPower Context triple: [United States, isMajorMilitaryPower, true]
-
A.
majorNonNATOAlly
Indicates that one entity has designated the other as a major non-NATO ally, granting it a special security and defense cooperation status outside the NATO alliance.
-
B.
majorPowerIn
chosen
Indicates that an entity holds significant political, economic, or military influence within a specified domain, region, or context.
-
C.
hasArmedForces
Indicates that an entity possesses or maintains organized military forces under its control.
-
D.
warPower
Indicates the authority, capability, or legal power to initiate, conduct, or manage acts of war or armed conflict.
-
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_69d87f1bb0988190b490d273dbf3fd03 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21a05148c8190bc2b98217fda23cc |
completed | April 17, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69e182885bc08190822ae7e8a4b8ac1f |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5:01 a.m.