Triple
T4612919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pax Americana |
E100800
|
entity |
| Predicate | securityOrder |
P3815
|
FINISHED |
| Object | U.S.-led alliance system |
—
|
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: U.S.-led alliance system | Statement: [Pax Americana, securityOrder, U.S.-led alliance system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityOrder Context triple: [Pax Americana, securityOrder, U.S.-led alliance system]
-
A.
securityArrangementsBy
Indicates that one entity is responsible for providing, organizing, or overseeing security arrangements for another entity or situation.
-
B.
securityOperation
Indicates an action or process carried out to protect, monitor, or defend assets, systems, or environments from threats or unauthorized activities.
-
C.
securityStatus
Indicates the current level or condition of protection, risk, or vulnerability associated with an entity or system.
-
D.
securityAspect
chosen
Indicates a relationship where something pertains to, represents, or characterizes a particular aspect or dimension of security.
-
E.
security
Indicates that an entity provides protection, safety measures, or safeguards to another entity or against specific threats or risks.
- 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.