Triple
T27388802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Friedrich Winnecke |
E691461
|
entity |
| Predicate | hasCommemorativeName |
P154143
|
FINISHED |
| Object | Winnecke 4 (asterism) |
—
|
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: Winnecke 4 (asterism) | Statement: [Friedrich Winnecke, hasCommemorativeName, Winnecke 4 (asterism)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommemorativeName Context triple: [Friedrich Winnecke, hasCommemorativeName, Winnecke 4 (asterism)]
-
A.
hasCommemorationName
chosen
Indicates that an entity has a specific name used to commemorate or honor a person, event, or concept.
-
B.
hasCommemorationFunction
Indicates that something serves the role or purpose of commemorating an event, person, group, or concept.
-
C.
hasCommemorativeObject
Indicates that one entity possesses or is associated with an object specifically intended to commemorate or honor a person, event, or occasion.
-
D.
previouslyCommemoratedBy
Indicates that an entity was honored or remembered in the past through a specific commemorative act, object, or event.
-
E.
hasCommemorationScope
Indicates the scope or extent of what is being commemorated in a commemoration-related relationship or event.
- 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_69ef520386788190bc92cfcd97ebb67a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69fef8c3f2388190b995ec173512945a |
completed | May 9, 2026, 9:05 a.m. |
| PD | Predicate disambiguation | batch_69fef65975608190960b78d27e806d4f |
completed | May 9, 2026, 8:54 a.m. |
Created at: April 27, 2026, 12:25 p.m.