Triple
T10136896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Odenwaldschule |
E226880
|
entity |
| Predicate | abusePubliclyExposed |
P92472
|
FINISHED |
| Object | 2010 |
—
|
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: 2010 | Statement: [Odenwaldschule, abusePubliclyExposed, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abusePubliclyExposed Context triple: [Odenwaldschule, abusePubliclyExposed, 2010]
-
A.
exposed
Indicates that one entity has been made visible, revealed, or left unprotected to another entity or to some external influence.
-
B.
exposedDuring
Indicates that something becomes visible, accessible, or subject to influence specifically within a given time period, event, or contextual interval.
-
C.
publiclyDisplayed
Indicates that something is shown or made visible in a public context or setting, accessible to people at large.
-
D.
exposedThrough
Indicates that something becomes revealed, accessible, or affected as a result of passing through or being subjected to another thing or medium.
-
E.
exposesTo
Indicates that one entity subjects another entity to contact with or influence from something, typically involving risk, effect, or experience.
- 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.