Triple
T23973884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lenzsche Regel |
E604308
|
entity |
| Predicate | wirdBehandeltIn |
P8558
|
FINISHED |
| Object | Schulphysik |
—
|
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: Schulphysik | Statement: [Lenzsche Regel, wirdBehandeltIn, Schulphysik]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wirdBehandeltIn Context triple: [Lenzsche Regel, wirdBehandeltIn, Schulphysik]
-
A.
treatsPatientsFrom
Indicates that a healthcare provider gives medical treatment or services to patients originating from a particular location or group.
-
B.
treatmentLocation
chosen
Indicates the place or facility where a treatment or medical intervention is administered to an entity.
-
C.
treatmentOf
Indicates a relationship where one entity administers, provides, or is responsible for a therapeutic intervention directed toward another entity (typically a patient or condition).
-
D.
treatmentCountry
Indicates the country where a treatment, therapy, or medical intervention is administered or takes place.
-
E.
commonlyPerformedIn
Indicates that an action or activity is typically or frequently carried out within a particular context, location, or setting.
- 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_69e29543019c8190872462e593cc50b4 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d1dda91c8190af716bceb3225aee |
completed | April 29, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:26 p.m.