Triple
T4612913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pax Americana |
E100800
|
entity |
| Predicate | supportedByPolicy |
P42489
|
FINISHED |
| Object | containment policy |
—
|
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: containment policy | Statement: [Pax Americana, supportedByPolicy, containment policy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportedByPolicy Context triple: [Pax Americana, supportedByPolicy, containment policy]
-
A.
supportsPolicy
Indicates that one entity endorses, backs, or is in favor of a particular policy or set of policies.
-
B.
hasPolicySupport
Indicates that one entity provides endorsement, backing, or approval for a specific policy associated with another entity.
-
C.
supportsPolicyGoal
Indicates that one entity’s actions, positions, or characteristics help advance, uphold, or contribute to achieving a specified policy goal.
-
D.
targetedByPolicy
chosen
Indicates that an entity is the intended subject or focus of a specific policy’s rules, actions, or effects.
-
E.
supportedByWork
Indicates that one entity’s existence, validity, or outcome is backed, justified, or enabled by the work or efforts 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_69bd43cf363c819087fd5ab441b4a3f4 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59c11f5481909f61e23503711cf5 |
completed | March 20, 2026, 2:29 p.m. |
| PD | Predicate disambiguation | batch_69bd522e2d5c8190937d0b5574f78f99 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:12 p.m.