Triple
T11230423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vice Admiral (United States Navy) |
E265803
|
entity |
| Predicate | rankType |
P97950
|
FINISHED |
| Object | line and staff corps |
—
|
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: line and staff corps | Statement: [Vice Admiral (United States Navy), rankType, line and staff corps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankType Context triple: [Vice Admiral (United States Navy), rankType, line and staff corps]
-
A.
rankingType
Indicates the specific basis or method by which items are ordered or ranked relative to one another.
-
B.
rankStatus
Indicates the hierarchical level or position an entity holds within an ordered ranking or status system.
-
C.
rankTier
Indicates the classification level or tier assigned to an entity within a ranking or hierarchical system.
-
D.
rankGrade
Indicates the grade or level assigned to an entity within a ranking or evaluation system.
-
E.
rankingScope
Indicates the context or domain within which a ranking is defined, interpreted, or applied.
- 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_69d6aac656d48190b275efaa7d6074ee |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e900fbcc8190a3177f8a73564433 |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d75cfdf7a88190aae21572e57ef208 |
completed | April 9, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69d77062271c8190b63da714ab5beff9 |
completed | April 9, 2026, 9:24 a.m. |
Created at: April 8, 2026, 9:30 p.m.