Triple
T1475317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wittenberg |
E30826
|
entity |
| Predicate | eventAssociated |
P19113
|
FINISHED |
| Object | start of the Protestant Reformation |
—
|
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: start of the Protestant Reformation | Statement: [Wittenberg, eventAssociated, start of the Protestant Reformation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventAssociated Context triple: [Wittenberg, eventAssociated, start of the Protestant Reformation]
-
A.
eventIn
chosen
Indicates that an event occurs within, or is situated in, a specific location, context, or larger event.
-
B.
eventRole
Indicates the specific function, capacity, or part an entity plays within an event or occurrence.
-
C.
event
Indicates that there exists an occurrence or happening involving one or more entities, typically situated in time and possibly space.
-
D.
eventUse
Indicates that an event involves the use or utilization of a particular entity (e.g., a resource, tool, or method) as part of its occurrence.
-
E.
eventInfluencedBy
Indicates that an event occurs or unfolds in a way that is causally or significantly affected by another entity, factor, or prior 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_69a498fe55a88190ab7f9e40ace88e49 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c602387c8190b97a20c8e05e3d16 |
completed | March 1, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69a4c484e52c81908948ff8c0a42751b |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:11 p.m.