Triple
T19312916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Park an der Ilm |
E483015
|
entity |
| Predicate | RomanHouseFunction |
P135550
|
FINISHED |
| Object | summer residence of Duke Carl August |
—
|
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: summer residence of Duke Carl August | Statement: [Park an der Ilm, RomanHouseFunction, summer residence of Duke Carl August]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RomanHouseFunction Context triple: [Park an der Ilm, RomanHouseFunction, summer residence of Duke Carl August]
-
A.
mainRomanSanctuary
Indicates that one entity serves as the primary Roman religious sanctuary or temple associated with another entity.
-
B.
house1
Indicates that something is identified or classified as a house or dwelling.
-
C.
ElizasHouseFunction
Indicates that something serves as the functional role, purpose, or use of Eliza’s house.
-
D.
housesFacility
Indicates that one entity serves as a location or container in which the other entity (a facility) is situated or operates.
-
E.
houseFounded
Indicates that an entity (such as a house, organization, or lineage) was established or created by another entity or at a specific time.
- F. None of above. chosen
Provenance (4 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_69d8e8d04d5c8190baa816986f2b1d1e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e604cf25c081908a30814b15d78c25 |
completed | April 20, 2026, 10:49 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0ef66881909d489d634eee817a |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4e4709d4481908c280cdd2ac18977 |
completed | April 19, 2026, 2:19 p.m. |
Created at: April 10, 2026, 1:32 p.m.