Triple
T32742097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Udo Proksch |
E837242
|
entity |
| Predicate | significantEventInLife |
P259
|
FINISHED |
| Object | exposure of the Lucona affair |
—
|
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: exposure of the Lucona affair | Statement: [Udo Proksch, significantEventInLife, exposure of the Lucona affair]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantEventInLife Context triple: [Udo Proksch, significantEventInLife, exposure of the Lucona affair]
-
A.
notableEventInLife
Indicates that a particular event holds significant importance or impact within an entity’s life or personal history.
-
B.
significantEvent
chosen
Indicates that an event involving the entities is of notable importance or impact within a given context.
-
C.
significantEventInvolves
Indicates that a significant event includes or engages a particular entity as a participant or key element.
-
D.
significantEventEnd
Indicates the point in time when a significant event or occurrence comes to a close or is considered finished.
-
E.
settingOfLifeEvents
Indicates the location or environment in which significant life events of an entity take place.
- 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_69f34936e1748190b797e406e4e9293a |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
Created at: May 1, 2026, 1:12 a.m.