Triple
T34698592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alex Kerner |
E891102
|
entity |
| Predicate | majorEventWitnessed |
P84985
|
FINISHED |
| Object | fall of the Berlin Wall |
—
|
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: fall of the Berlin Wall | Statement: [Alex Kerner, majorEventWitnessed, fall of the Berlin Wall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorEventWitnessed Context triple: [Alex Kerner, majorEventWitnessed, fall of the Berlin Wall]
-
A.
historicalEventWitnessed
chosen
Indicates that an entity personally observed or was present at a particular historical event.
-
B.
significantEventInvolves
Indicates that a significant event includes or engages a particular entity as a participant or key element.
-
C.
isMajorEventOf
Indicates that an event is a primary, significant, or defining occurrence within the context of another entity (such as a project, period, or process).
-
D.
significantEvent
Indicates that an event involving the entities is of notable importance or impact within a given context.
-
E.
significantEventDocumented
Indicates that a notable or impactful event has been formally recorded or documented in some medium.
- 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_69f349db7ab8819086808e833f472871 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff63e6b61081909c648bf0ff279481 |
completed | May 9, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69ff6381867881908ae0545df4b71df5 |
completed | May 9, 2026, 4:40 p.m. |
Created at: May 1, 2026, 2:05 a.m.