Triple
T175186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ANZUS |
E3557
|
entity |
| Predicate | typeOfObligation |
P445
|
FINISHED |
| Object | consultation in event of armed attack in the Pacific |
—
|
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: consultation in event of armed attack in the Pacific | Statement: [ANZUS, typeOfObligation, consultation in event of armed attack in the Pacific]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfObligation Context triple: [ANZUS, typeOfObligation, consultation in event of armed attack in the Pacific]
-
A.
obligationType
chosen
Indicates the specific kind or category of duty, requirement, or commitment that applies within an obligation relationship.
-
B.
typeOfContract
Indicates the specific kind or category of contractual agreement that applies between the related entities.
-
C.
isSubjectTo
Indicates that one entity is governed, affected, or constrained by the authority, rules, conditions, or influence of another entity.
-
D.
obeysLaw
Indicates that an entity follows, complies with, or acts in accordance with a specified law or set of laws.
-
E.
requires
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
- 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_69a25374990081909766d30c79a18e0e |
completed | Feb. 28, 2026, 2:31 a.m. |
| NER | Named-entity recognition | batch_69a258e32da88190ad9485aecd0bf08f |
completed | Feb. 28, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69a25669d99481908c5e82ba8641205a |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:39 a.m.