Triple

T25176597
Position Surface form Disambiguated ID Type / Status
Subject HMAS Warramunga (FFH 152) E630463 entity
Predicate allianceActivity P41664 FINISHED
Object exercises with United States Navy 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: exercises with United States Navy | Statement: [HMAS Warramunga (FFH 152), allianceActivity, exercises with United States Navy]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: allianceActivity
Context triple: [HMAS Warramunga (FFH 152), allianceActivity, exercises with United States Navy]
  • A. allianceInteraction chosen
    Indicates an interaction or cooperative engagement occurring specifically between allied entities within an alliance.
  • B. allianceProject
    Indicates a collaborative project or initiative jointly undertaken by allied entities within an alliance relationship.
  • C. associatedTribeActivity
    Indicates a relationship where a specific activity is linked to, practiced by, or characteristic of a particular tribe.
  • D. involvesAlliance
    Indicates that there exists a cooperative or strategic alliance relationship between the referenced entities.
  • E. alliancesAround
    Indicates that alliances are formed or exist in the vicinity or context of a specified entity or focal point.
  • 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_69e75a88fdf081908e47ae6e195c14e1 completed April 21, 2026, 11:07 a.m.
NER Named-entity recognition batch_69f46dc040088190958bb7a6633fd016 completed May 1, 2026, 9:09 a.m.
PD Predicate disambiguation batch_69f44d8043b081908bbffd7f044b4f26 completed May 1, 2026, 6:51 a.m.
Created at: April 21, 2026, 12:34 p.m.