Triple
T30301772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DD-421 |
E770668
|
entity |
| Predicate | namesakeOccupationHolder |
P117536
|
FINISHED |
| Object | Admiral William S. Benson |
—
|
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: Admiral William S. Benson | Statement: [DD-421, namesakeOccupationHolder, Admiral William S. Benson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namesakeOccupationHolder Context triple: [DD-421, namesakeOccupationHolder, Admiral William S. Benson]
-
A.
namesakeOccupation
Indicates that one entity’s occupation is the same as, or derived from, the occupation associated with the other entity’s namesake.
-
B.
namesakeDescription
Indicates that the object provides a descriptive explanation of why or how the subject is considered a namesake of something or someone.
-
C.
namedPersonOccupation
Indicates that a person is explicitly identified as having a particular occupation or job role.
-
D.
namesakeNationality
Indicates that one entity has the same nationality as the person or entity after whom it is named.
-
E.
namedAfterOccupationOrRole
chosen
Indicates that an entity is named after a specific occupation, profession, or social role associated with a person or group.
- 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_69f224881b948190b8c4921b250a44a3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6813b03c881909786514932f103f3 |
completed | May 2, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:48 p.m.