Triple
T36947551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maria Enders |
E913955
|
entity |
| Predicate | hasAgentWithinStory |
P19389
|
FINISHED |
| Object | Klaus Diesterweg |
—
|
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: Klaus Diesterweg | Statement: [Maria Enders, hasAgentWithinStory, Klaus Diesterweg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAgentWithinStory Context triple: [Maria Enders, hasAgentWithinStory, Klaus Diesterweg]
-
A.
hasAgent
chosen
Indicates that an action or event is carried out or initiated by a particular agent.
-
B.
hasAllyInStory
Indicates that one entity is portrayed as an ally or supportive partner of another entity within the context of a specific story or narrative.
-
C.
hasSiblingInStory
Indicates that one character in a narrative has at least one sibling who also appears within the same story.
-
D.
hasLeaderInStory
Indicates that one entity serves as the leader of another entity within the context of a specific story or narrative.
-
E.
hasStaffTypeInStory
Indicates that a story involves or is associated with a particular type or category of staff.
- 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_69f76e8b28848190abd81fe7a7374910 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:13 p.m.