Triple
T10136906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Odenwaldschule |
E226880
|
entity |
| Predicate | closureDecision |
P92473
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [Odenwaldschule, closureDecision, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closureDecision Context triple: [Odenwaldschule, closureDecision, 2015]
-
A.
closureReason
Indicates the reason or cause for which an entity, process, or case has been closed or terminated.
-
B.
closingOutcome
Indicates the result or consequence that follows from a closing action or the completion of a closure process between entities.
-
C.
closureProcess
Indicates the procedure or set of actions carried out to formally conclude, finalize, or terminate an ongoing activity, case, or process.
-
D.
closure
Indicates that an entity is closed or not accessible/available for use, entry, or interaction.
-
E.
closingSituation
Indicates a situation or context in which an interaction, event, or process is coming to an end or being brought to a close.
- F. None of above. chosen
Provenance (4 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_69ca8433ec308190b8b25a6fe359c34c |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cde881a2188190a5e519b90a1b910b |
completed | April 2, 2026, 3:54 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba4f5d88190ba68e63be10b08c7 |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd51bc440c819086320900701f87c2 |
completed | April 1, 2026, 5:11 p.m. |
Created at: March 30, 2026, 9:06 p.m.