Triple
T38094743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schönbrunn Palace Gardens |
E951212
|
entity |
| Predicate | principalDesigner |
P28525
|
FINISHED |
| Object | Johann Bernhard Fischer von Erlach |
—
|
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: Johann Bernhard Fischer von Erlach | Statement: [Schönbrunn Palace Gardens, principalDesigner, Johann Bernhard Fischer von Erlach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: principalDesigner Context triple: [Schönbrunn Palace Gardens, principalDesigner, Johann Bernhard Fischer von Erlach]
-
A.
principalArchitect
Indicates that one entity serves as the lead or primary architect responsible for the design or architectural direction of another entity.
-
B.
designedBy
Indicates that one entity is the creator, planner, or architect responsible for the form or structure of another entity.
-
C.
designerAlias
Indicates that one name or label is used as an alternative alias for a designer.
-
D.
designerType
Indicates the specific kind or category of designer role associated with an entity.
-
E.
designLead
chosen
Indicates that one entity serves as the primary designer or person in charge of leading the design work for another entity or project.
- 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_69f76f04960c8190a83f14ae4c67f5bc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:21 p.m.