Triple
T31750901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Flaherty (DE-135) |
E810413
|
entity |
| Predicate | nameHonor |
P46466
|
FINISHED |
| Object | Ensign Francis C. Flaherty, USNR |
—
|
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: Ensign Francis C. Flaherty, USNR | Statement: [USS Flaherty (DE-135), nameHonor, Ensign Francis C. Flaherty, USNR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameHonor Context triple: [USS Flaherty (DE-135), nameHonor, Ensign Francis C. Flaherty, USNR]
-
A.
nameHonors
chosen
Indicates that a name is given to honor, commemorate, or pay tribute to a particular entity.
-
B.
honorificPartOfName
Indicates that an honorific title or form of address is included as part of a person's full name.
-
C.
nameBearerHonor
Indicates that an entity bears or carries a name as an honor or mark of respect bestowed by another entity.
-
D.
honorificNameOf
Indicates that one entity is the honorific or respectful name or title used to refer to another entity.
-
E.
honorificNickname
Indicates that one entity is referred to by a respectful or honorific nickname by another entity or in a given context.
- 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_69f348e340d48190b780fae618c51464 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6ab5262c88190bc54527b57ec2a81 |
completed | May 3, 2026, 1:56 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:28 p.m.