Triple
T37831354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Johnston (DD-821) |
E943210
|
entity |
| Predicate | honorsCommanderName |
P46466
|
FINISHED |
| Object | Ernest E. Evans |
—
|
NE NERFINISHED |
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: Ernest E. Evans | Statement: [USS Johnston (DD-821), honorsCommanderName, Ernest E. Evans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorsCommanderName Context triple: [USS Johnston (DD-821), honorsCommanderName, Ernest E. Evans]
-
A.
commanderTitle
Indicates the official rank or title held by the person who commands or leads a given entity.
-
B.
laterTitleOfCommander
Indicates that one title represents a later-held command position of the same commander who previously held another title.
-
C.
honorRank
Indicates a hierarchical relationship where one entity holds a particular level or position of honor or prestige relative to others.
-
D.
nameHonors
chosen
Indicates that a name is given to honor, commemorate, or pay tribute to a particular entity.
-
E.
commanderFullName
Indicates that the predicate specifies the complete personal name of the commander associated with an entity.
- 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_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: May 3, 2026, 4:19 p.m.