Triple
T25155924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heiligenkreuz Abbey |
E626311
|
entity |
| Predicate | hasMusicSchool |
P55412
|
FINISHED |
| Object | Schola Gregoriana Heiligenkreuz |
—
|
NE NERFINISHED |
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: Schola Gregoriana Heiligenkreuz | Statement: [Heiligenkreuz Abbey, hasMusicSchool, Schola Gregoriana Heiligenkreuz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMusicSchool Context triple: [Heiligenkreuz Abbey, hasMusicSchool, Schola Gregoriana Heiligenkreuz]
-
A.
hasMusicInstitution
chosen
Indicates that an entity is associated with or hosts a music-related institution, such as a conservatory, music school, or similar organization.
-
B.
hasMusicFacility
Indicates that an entity provides or includes a dedicated facility or resources for music-related activities.
-
C.
hasArtisticSchool
Indicates that an entity is associated with, belongs to, or is characterized by a particular artistic school or style.
-
D.
hasConservatoryType
Indicates the specific type or classification of a conservatory associated with an entity.
-
E.
hasSchoolIn
Indicates that a school is located within or operates in a specified place or region.
- 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_69e2ff2834ec8190b0872e2ec3d76023 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 18, 2026, 6:30 a.m.