Triple
T36916163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australia–Japan relations |
E913049
|
entity |
| Predicate | majorSecurityAgreement |
P90911
|
FINISHED |
| Object | Japan–Australia Reciprocal Access Agreement |
—
|
NE NERFINISHED |
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: Japan–Australia Reciprocal Access Agreement | Statement: [Australia–Japan relations, majorSecurityAgreement, Japan–Australia Reciprocal Access Agreement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorSecurityAgreement Context triple: [Australia–Japan relations, majorSecurityAgreement, Japan–Australia Reciprocal Access Agreement]
-
A.
majorSecurityDeclaration
Indicates a formal, high-level statement or commitment regarding security policies, intentions, or obligations between entities.
-
B.
signedMajorTreaty
Indicates that an entity formally entered into and approved a significant, binding treaty with another party or parties.
-
C.
defenseAgreement
chosen
Indicates the existence of a formal or informal pact in which parties commit to support or protect each other in matters of defense or security.
-
D.
majorSecurityIssue
Indicates that the subject faces or causes a significant security vulnerability or threat.
-
E.
tradeAgreementSigned
Indicates that a formal trade agreement has been officially concluded and signed between the involved parties.
- 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_69f76e885b848190bad82c87e9525486 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffe01c9d3c819084c256bb3c81c0dc |
completed | May 10, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69ffdfcc78b08190aa4493f13d62a531 |
completed | May 10, 2026, 1:30 a.m. |
Created at: May 3, 2026, 4:13 p.m.