Triple
T9890808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quadrilateral Security Dialogue |
E181443
|
entity |
| Predicate | notFormalAlliance |
P91016
|
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: [Quadrilateral Security Dialogue, notFormalAlliance, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notFormalAlliance Context triple: [Quadrilateral Security Dialogue, notFormalAlliance, true]
-
A.
alliance
Indicates a formal cooperative relationship between entities who agree to support each other in shared goals or interests.
-
B.
doesNotHaveFormalPeaceTreatyWith
Indicates that no official, legally binding peace treaty exists between the two entities.
-
C.
soughtAllianceWith
Indicates that one entity actively attempted to form an alliance or cooperative partnership with another entity.
-
D.
opposingAlliance
Indicates that two entities belong to rival or mutually opposed alliances or factions.
-
E.
nonGovernmental
Indicates that an entity, action, or relationship is not associated with, controlled by, or part of a government or governmental body.
- F. None of above. chosen
Provenance (4 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_69ca8283a6708190801af7a25a7ebb9f |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb47dfa908190884e96e5e5d6f41f |
completed | April 2, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69cd1d872d50819096b7ab166a8decf1 |
completed | April 1, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69cd3581a9688190a00cef4c3eebb0ae |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:39 p.m.