Triple
T35105536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carl Ludwig Willdenow |
E1013141
|
entity |
| Predicate | hasHonorificAbbreviation |
P195107
|
FINISHED |
| Object | Willd. |
—
|
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: Willd. | Statement: [Carl Ludwig Willdenow, hasHonorificAbbreviation, Willd.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHonorificAbbreviation Context triple: [Carl Ludwig Willdenow, hasHonorificAbbreviation, Willd.]
-
A.
hasHonorificName
Indicates that an entity is referred to by a formal or respectful title or name used as an honorific.
-
B.
hasHonorificFrom
Indicates that one entity uses or receives a particular honorific title or form of address originating from another entity or source.
-
C.
hasHonorificPrefix
Indicates that one entity is used as an honorific title or prefix attached to another entity’s name.
-
D.
hasHonorificDescription
Indicates that an entity is associated with an honorific title or descriptive phrase expressing respect or formal status.
-
E.
hasHonorificBasis
Indicates that one entity serves as the basis or justification for assigning an honorific title or respectful form of address 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_69f76dd556248190808b4c4f43debebb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
| PDg | Predicate description generation | batch_69fda4fe67a08190bdaa84ceabd6de6c |
completed | May 8, 2026, 8:55 a.m. |
Created at: May 3, 2026, 4:01 p.m.