Triple
T34003945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stormarnschule Ahrensburg |
E871904
|
entity |
| Predicate | hasSchoolFocus |
P19184
|
FINISHED |
| Object | academic education |
—
|
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: academic education | Statement: [Stormarnschule Ahrensburg, hasSchoolFocus, academic education]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSchoolFocus Context triple: [Stormarnschule Ahrensburg, hasSchoolFocus, academic education]
-
A.
hasSchool
Indicates that an entity possesses, is associated with, or is served by a particular school.
-
B.
hasSchoolIn
Indicates that a school is located within or operates in a specified place or region.
-
C.
hasSchoolCategory
chosen
Indicates that an entity (such as a school or educational institution) is associated with a particular category or type of school.
-
D.
hasSchoolsAccess
Indicates that one entity has permission or the ability to access schools or school-related resources associated with another entity.
-
E.
hasSpecializedSchool
Indicates that an entity operates or is associated with a school focused on a specific field, discipline, or specialized type of education.
- 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_69f3499f8cbc81908de6ec89fa91ea8f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd0b92f42881908cd77e3f058adcc2 |
completed | May 7, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fd0a3d68d4819094d92040f7c48d7c |
completed | May 7, 2026, 9:55 p.m. |
Created at: May 1, 2026, 1:50 a.m.