Triple
T11230417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vice Admiral (United States Navy) |
E265803
|
entity |
| Predicate | typicalBilletType |
P90904
|
FINISHED |
| Object | operational command |
—
|
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: operational command | Statement: [Vice Admiral (United States Navy), typicalBilletType, operational command]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBilletType Context triple: [Vice Admiral (United States Navy), typicalBilletType, operational command]
-
A.
typicalBillet
chosen
Indicates that something serves as a standard or characteristic billet or assignment for a given role, context, or entity.
-
B.
typicalBilletsInclude
Indicates that certain items or roles are commonly or normally included within a given set of billets.
-
C.
ticketTypeExample
Indicates that an entity serves as an example or illustrative instance of a particular ticket type.
-
D.
typicalTicketText
Indicates that the associated text represents the standard or commonly used wording for a ticket.
-
E.
ticketMediumType
Indicates the type or format of the medium through which a ticket is issued, stored, or presented (e.g., paper, mobile, electronic).
- 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_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. |
Created at: April 8, 2026, 9:30 p.m.