Triple
T25842716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian Defence Force Reserves |
E650978
|
entity |
| Predicate | hasPersonnelCategory |
P11881
|
FINISHED |
| Object | officers |
—
|
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: officers | Statement: [Australian Defence Force Reserves, hasPersonnelCategory, officers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPersonnelCategory Context triple: [Australian Defence Force Reserves, hasPersonnelCategory, officers]
-
A.
personnelType
chosen
Indicates the classification or role category assigned to a person within an organization or system.
-
B.
usesStaffCategory
Indicates that an entity employs or applies a particular category or classification of staff in its operations or context.
-
C.
designationCategory
Indicates the classification or type of designation assigned to an entity within a broader designation system.
-
D.
isCategoryOfPeople
Indicates that a group or classification specifically pertains to people as its members.
-
E.
roleInPersonnelMatters
Indicates that one entity has a specific function, authority, or involvement in managing or deciding personnel-related matters concerning 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_69e7ab38086081908f3a8e7e0c6efd83 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 22, 2026, 7:50 a.m.