Triple
T37831353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Johnston (DD-821) |
E943210
|
entity |
| Predicate | honorsCommanderRank |
P30999
|
FINISHED |
| Object | Commander |
—
|
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: Commander | Statement: [USS Johnston (DD-821), honorsCommanderRank, Commander]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorsCommanderRank Context triple: [USS Johnston (DD-821), honorsCommanderRank, Commander]
-
A.
honorRank
Indicates a hierarchical relationship where one entity holds a particular level or position of honor or prestige relative to others.
-
B.
hasCommanderRank
chosen
Indicates that an entity holds the military or organizational rank of commander within a specified hierarchy or context.
-
C.
honoraryRankGrantedBy
Indicates that an entity has been awarded an honorary rank or title by another entity or authority.
-
D.
honorificRank
Indicates that one entity holds a formal title or honorific status in relation to another entity.
-
E.
commandingOfficerRank
Indicates the military rank held by the officer who has command authority over a given individual or unit.
- 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_69f76eea4c8c8190a335aed5955cf2db |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:19 p.m.