Triple
T28587578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bavarian Palace Department |
E723550
|
entity |
| Predicate | ownedOrOperatedSite |
P13496
|
FINISHED |
| Object | Nymphenburg Palace |
—
|
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: Nymphenburg Palace | Statement: [Bavarian Palace Department, ownedOrOperatedSite, Nymphenburg Palace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownedOrOperatedSite Context triple: [Bavarian Palace Department, ownedOrOperatedSite, Nymphenburg Palace]
-
A.
ownedAndOperatedStatus
Indicates that one entity both owns and actively operates another entity, such as a business, facility, or asset.
-
B.
ownsOrManages
chosen
Indicates that one entity has ownership of, or managerial control over, another entity.
-
C.
operatesOnSiteType
Indicates that an entity conducts its operations or activities at, or in association with, a specified type of site or location.
-
D.
hasSiteUse
Indicates that a site is used or designated for a particular function, activity, or purpose.
-
E.
heritageDesignationOfSiteOperated
Indicates that a site being operated has been granted a specific heritage designation or status.
- 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_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 4:18 a.m.