Triple
T32583779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bennie G. Thompson |
E832861
|
entity |
| Predicate | has honorific prefix |
P368
|
FINISHED |
| Object | The Honorable |
—
|
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: The Honorable | Statement: [Bennie G. Thompson, has honorific prefix, The Honorable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: has honorific prefix Context triple: [Bennie G. Thompson, has honorific prefix, The Honorable]
-
A.
honorificPrefix
Indicates the formal title or respectful prefix (e.g., "Dr.", "Mr.", "Prof.") used before a person's name to denote status, role, or honor.
-
B.
hasHonorificPrefix
chosen
Indicates that one entity is used as an honorific title or prefix attached to another entity’s name.
-
C.
hasHonorificName
Indicates that an entity is referred to by a formal or respectful title or name used as an honorific.
-
D.
honorificPartOfName
Indicates that an honorific title or form of address is included as part of a person's full name.
-
E.
hasHonorificSystem
Indicates that a language or culture employs a structured system of honorifics to mark social status, respect, or formality in communication.
- 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_69f349289adc81909f4374a58ec35a39 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c66c41b481908abc65d5d284bcee |
completed | May 3, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2c138481908afa3ee3e91f8900 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:04 a.m.