Triple
T19641382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States–Australia relations |
E471547
|
entity |
| Predicate | allianceCameIntoForce |
P23002
|
FINISHED |
| Object | 1952 |
—
|
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: 1952 | Statement: [United States–Australia relations, allianceCameIntoForce, 1952]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allianceCameIntoForce Context triple: [United States–Australia relations, allianceCameIntoForce, 1952]
-
A.
alliance
Indicates a formal cooperative relationship between entities who agree to support each other in shared goals or interests.
-
B.
allianceCreated
chosen
Indicates that a formal cooperative relationship or partnership has been established between two or more parties.
-
C.
soughtAllianceWith
Indicates that one entity actively attempted to form an alliance or cooperative partnership with another entity.
-
D.
formedAllianceThrough
Indicates that two or more parties established an alliance specifically by means of, or as a result of, a particular event, action, or intermediary.
-
E.
allianceUse
Indicates that one party makes use of, benefits from, or leverages an alliance or allied relationship with another party.
- 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_69d8e511f28481909f4bc3ea9191e54a |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e6412224d481909524d7654a36d49b |
completed | April 20, 2026, 3:07 p.m. |
| PD | Predicate disambiguation | batch_69e514e5cb108190ae260e466c447314 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:44 p.m.