Triple
T16949017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sergeants Major Course |
E411136
|
entity |
| Predicate | designedForRank |
P125347
|
FINISHED |
| Object | E-9 |
—
|
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: E-9 | Statement: [Sergeants Major Course, designedForRank, E-9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForRank Context triple: [Sergeants Major Course, designedForRank, E-9]
-
A.
namedForRank
Indicates that something is named after a specific rank or title held by an entity.
-
B.
isRanked
Indicates that an entity has been assigned a position or level within an ordered hierarchy or comparative list.
-
C.
rankedAs
Indicates that one entity is assigned a specific position or level in an ordered ranking relative to others.
-
D.
representsRank
Indicates that one entity serves as the rank, status, or hierarchical level assigned to another entity.
-
E.
usesRank
Indicates that one entity applies or relies on a ranking or ordered level system associated with another entity.
- F. None of above. chosen
Provenance (4 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cfb4b1b08190b608d36a209ed6bd |
completed | April 18, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e355722040819098830dabf207ecd6 |
completed | April 18, 2026, 9:57 a.m. |
Created at: April 10, 2026, 5:31 a.m.