Triple
T5528898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senior Leader Course for infantry NCOs |
E144996
|
entity |
| Predicate | targetRankLevel |
P34581
|
FINISHED |
| Object | mid-career NCOs |
—
|
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: mid-career NCOs | Statement: [Senior Leader Course for infantry NCOs, targetRankLevel, mid-career NCOs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetRankLevel Context triple: [Senior Leader Course for infantry NCOs, targetRankLevel, mid-career NCOs]
-
A.
rankTier
Indicates the classification level or tier assigned to an entity within a ranking or hierarchical system.
-
B.
teamLevel
Indicates the hierarchical rank or tier at which a team operates within an organization, competition, or structure.
-
C.
hasRankLevels
chosen
Indicates that an entity is associated with one or more hierarchical rank levels within a ranking or grading system.
-
D.
eligibleRank
Indicates that an entity meets the required rank or level criteria to qualify for a specific role, action, or benefit.
-
E.
highestRankIn
Indicates that one entity holds the top or most senior rank within a specified group, category, or context relative to other entities.
- 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_69c008f9955881909bfa8348b56b4739 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f8b6c348190b7d414dc1907d09a |
completed | March 22, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69c01b0c50e48190a1b03ecd20ca440b |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:34 p.m.