Triple
T15322969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drill Instructors of MCRD San Diego |
E366338
|
entity |
| Predicate | typicalRanks |
P9317
|
FINISHED |
| Object | sergeant |
—
|
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: sergeant | Statement: [Drill Instructors of MCRD San Diego, typicalRanks, sergeant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRanks Context triple: [Drill Instructors of MCRD San Diego, typicalRanks, sergeant]
-
A.
typicalRank
chosen
Indicates the usual or most common rank or position an entity holds within a given ordering or hierarchy.
-
B.
typicalRankRange
Indicates the usual or most common range of ranks or ordered positions that an entity typically occupies within a ranking or hierarchy.
-
C.
canonicalRank
Indicates the standard or officially recognized rank or level assigned to an entity within an ordered hierarchy.
-
D.
tensorRank
Indicates the rank (number of indices or dimensions) associated with a given tensor.
-
E.
hasRankOrder
Indicates that one entity is ordered or positioned relative to others according to a specific ranking or sequence.
- 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_69d85a121520819093dcce999fdefe1a |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03dd5ce0c819093c9a14de549dff6 |
completed | April 16, 2026, 1:39 a.m. |
| PD | Predicate disambiguation | batch_69deca9659f48190b8661df223ce5078 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:16 a.m.