Triple
T38226739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army Chief Warrant Officer 3 (W-3) |
E1012164
|
entity |
| Predicate | rankHierarchy |
P37057
|
FINISHED |
| Object | mid-level technical and tactical leader |
—
|
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-level technical and tactical leader | Statement: [Army Chief Warrant Officer 3 (W-3), rankHierarchy, mid-level technical and tactical leader]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankHierarchy Context triple: [Army Chief Warrant Officer 3 (W-3), rankHierarchy, mid-level technical and tactical leader]
-
A.
rankType
Indicates the specific category or classification of a rank within a ranking or hierarchy system.
-
B.
rankEquivalent
Indicates that two entities hold the same rank or hierarchical level within a given ordering or classification system.
-
C.
rankTier
chosen
Indicates the classification level or tier assigned to an entity within a ranking or hierarchical system.
-
D.
rankInformation
Indicates that information is being ordered or prioritized according to some ranking criteria or relevance.
-
E.
rankGrade
Indicates the grade or level assigned to an entity within a ranking or evaluation 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_69f76dd25e0c81909f2abd0803e5e3ee |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:30 p.m.