Triple

T14448508
Position Surface form Disambiguated ID Type / Status
Subject Australian Corps E358266 entity
Predicate hasNationalityOfPersonnel P14610 FINISHED
Object Australian 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: Australian | Statement: [Australian Corps, hasNationalityOfPersonnel, Australian]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNationalityOfPersonnel
Context triple: [Australian Corps, hasNationalityOfPersonnel, Australian]
  • A. nationalityOfPersonnel chosen
    Indicates the country or countries to which the personnel involved in an activity, organization, or context belong by citizenship or national affiliation.
  • B. hasNationalityRecord
    Indicates that there exists an official record documenting an entity's nationality or national affiliation.
  • C. nationalityOfOfficerOnWatch
    Indicates the country or national affiliation of the officer currently on watch.
  • D. hasMilitaryStatus
    Indicates that an entity possesses a specific military affiliation, role, or status (such as active duty, reserve, or veteran).
  • E. hasMilitaryAuthority
    Indicates that one entity possesses formal power or command to direct, control, or make decisions over the military activities or forces of another entity.
  • 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_69d82794dfa081909b9134ad2e32244b completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de916139888190be219678e29a2a3a completed April 14, 2026, 7:11 p.m.
PD Predicate disambiguation batch_69de5c3a02fc819097373f97a260cdeb completed April 14, 2026, 3:24 p.m.
Created at: April 10, 2026, 1:19 a.m.