Triple
T38631549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Formal Learning Centers of the Marine Corps |
E937466
|
entity |
| Predicate | targetRankRange |
P16498
|
FINISHED |
| Object | entry‑level through senior enlisted |
—
|
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: entry‑level through senior enlisted | Statement: [Formal Learning Centers of the Marine Corps, targetRankRange, entry‑level through senior enlisted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetRankRange Context triple: [Formal Learning Centers of the Marine Corps, targetRankRange, entry‑level through senior enlisted]
-
A.
rankRange
chosen
Indicates that an entity’s rank falls within a specified minimum and maximum range.
-
B.
rankingPointsRange
Indicates the range of ranking points assigned or applicable to an entity within a ranking or scoring system.
-
C.
rankingScope
Indicates the context or domain within which a ranking is defined, interpreted, or applied.
-
D.
containsRank
Indicates that one entity includes or encompasses another entity that has a specific rank or hierarchical level within it.
-
E.
rankTier
Indicates the classification level or tier assigned to an entity within a ranking or hierarchical 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_69f76ed5ca3c81909288f61fbf37b359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff65987ff88190b09be64f7c0e1da9 |
completed | May 9, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69ff6525b0548190bef7a9f009e00bb8 |
completed | May 9, 2026, 4:47 p.m. |
Created at: May 3, 2026, 4:32 p.m.