Triple
T29554235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australia and Indonesia |
E749860
|
entity |
| Predicate | LombokTreatyCovers |
P144666
|
FINISHED |
| Object | defence cooperation |
—
|
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: defence cooperation | Statement: [Australia and Indonesia, LombokTreatyCovers, defence cooperation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: LombokTreatyCovers Context triple: [Australia and Indonesia, LombokTreatyCovers, defence cooperation]
-
A.
linkedToTreaty
Indicates that an entity has a formal connection or association with a specific treaty, such as being established by, governed by, or otherwise related to that treaty.
-
B.
treatySignedFor
Indicates that a formal treaty has been signed on behalf of, or in representation of, a particular entity, cause, or subject.
-
C.
treatyFeature
chosen
Indicates that one entity is a characteristic, provision, or specific element that forms part of a treaty.
-
D.
treatyAlsoKnownAs
Indicates that a treaty is referred to by an alternative name or alias.
-
E.
linkedTreaty
Indicates that there is a formal treaty connection or association between the related entities, such as being parties to, or otherwise bound by, the same treaty.
- 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_69f0bd4919e48190942b2a13d5b97d03 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 5:15 p.m.