Triple
T30998582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regular Force (NZDF) |
E789871
|
entity |
| Predicate | includesRankStructure |
P36072
|
FINISHED |
| Object | commissioned 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: commissioned officers | Statement: [Regular Force (NZDF), includesRankStructure, commissioned officers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesRankStructure Context triple: [Regular Force (NZDF), includesRankStructure, commissioned officers]
-
A.
rankStructureIncludes
chosen
Indicates that a given rank structure contains or encompasses a specified rank or set of ranks within its hierarchy.
-
B.
usesRankStructure
Indicates that an entity organizes its members or components according to a defined hierarchical rank structure.
-
C.
includesRankCategory
Indicates that one entity’s set of ranks or classifications contains or encompasses a particular rank category.
-
D.
containsRank
Indicates that one entity includes or encompasses another entity that has a specific rank or hierarchical level within it.
-
E.
hasRankLevels
Indicates that an entity is associated with one or more hierarchical rank levels within a ranking or grading system.
- 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_69f224c65a348190baaed1c01a29900c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a00b7fb90f881908f73edf2be8cc3a5 |
completed | May 10, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_6a00b75593d08190b3e76191cd79cdec |
completed | May 10, 2026, 4:50 p.m. |
Created at: April 29, 2026, 8:56 p.m.