Triple
T24132310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Navy Medical Service Corps officers |
E597986
|
entity |
| Predicate | typicalRankPrefix |
P154962
|
FINISHED |
| Object | Lieutenant (junior grade) |
—
|
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: Lieutenant (junior grade) | Statement: [Navy Medical Service Corps officers, typicalRankPrefix, Lieutenant (junior grade)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRankPrefix Context triple: [Navy Medical Service Corps officers, typicalRankPrefix, Lieutenant (junior grade)]
-
A.
typicalRank
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.
representsRank
Indicates that one entity serves as the rank, status, or hierarchical level assigned to 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_69e288c808b881909fed7d18f04bcbbe |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1df78b6f08190809fc154110fa201 |
completed | April 29, 2026, 10:37 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
| PDg | Predicate description generation | batch_69f17c28b684819084eea522126463f8 |
completed | April 29, 2026, 3:34 a.m. |
Created at: April 17, 2026, 11:25 p.m.