Triple
T29810737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maximilianeum Foundation for gifted students |
E756955
|
entity |
| Predicate | residenceProvidedAt |
P50598
|
FINISHED |
| Object | Maximilianeum |
—
|
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: Maximilianeum | Statement: [Maximilianeum Foundation for gifted students, residenceProvidedAt, Maximilianeum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: residenceProvidedAt Context triple: [Maximilianeum Foundation for gifted students, residenceProvidedAt, Maximilianeum]
-
A.
usedAsOfficialResidenceSince
Indicates that an entity has served as the formally designated official residence of another entity starting from a specified point in time.
-
B.
inResidenceAt
Indicates that an entity lives or resides at a particular location or residence.
-
C.
residenceDuringEvent
Indicates that an entity resides or is located at a particular place for the duration of a specified event.
-
D.
grantedResidence
chosen
Indicates that one entity has officially conferred the right to reside or live in a place or jurisdiction to another entity.
-
E.
residencyAt
Indicates that an entity lives or has an established residence at a particular location or address.
- 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_69f2245584848190ad4cab1f07752ccb |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67f7efc3c8190986d2d95b7a23729 |
completed | May 2, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 5:23 p.m.