Triple
T22067501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | August Wilhelm von Hofmann |
E545313
|
entity |
| Predicate | honorificPartOfName |
P146484
|
FINISHED |
| Object | von |
—
|
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: von | Statement: [August Wilhelm von Hofmann, honorificPartOfName, von]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorificPartOfName Context triple: [August Wilhelm von Hofmann, honorificPartOfName, von]
-
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.
honorificInitial
Indicates that one entity is the initial letter or abbreviated form of an honorific title used for another entity.
-
C.
honorificNameOf
Indicates that one entity is the honorific or respectful name or title used to refer to another entity.
-
D.
honorificSuffix
Indicates that one entity is a respectful or formal suffix appended to another entity’s name or title.
-
E.
honorificTitle
Indicates that one entity serves as a formal honorific or respectful title used to address or refer to another entity.
- F. None of above. chosen
Provenance (4 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_69e11e344dfc81909b1d88a7221329c7 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12884937c819095d3af69123fa2cb |
completed | April 28, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69e6f64a6a70819089d1a6c3a2384861 |
completed | April 21, 2026, 4 a.m. |
| PDg | Predicate description generation | batch_69e6fad4a540819096cdd5ea08527220 |
completed | April 21, 2026, 4:19 a.m. |
Created at: April 16, 2026, 8:27 p.m.