Triple
T8389235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pagodenburg |
E197898
|
entity |
| Predicate | hasGardenContext |
P12538
|
FINISHED |
| Object | formal Baroque garden setting |
—
|
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: formal Baroque garden setting | Statement: [Pagodenburg, hasGardenContext, formal Baroque garden setting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGardenContext Context triple: [Pagodenburg, hasGardenContext, formal Baroque garden setting]
-
A.
containsGarden
Indicates that one entity includes or has a garden within its area or boundaries.
-
B.
hasGardenType
chosen
Indicates that an entity possesses or is associated with a garden of a specified type.
-
C.
hasGardenSquare
Indicates that an entity includes, is adjacent to, or is otherwise associated with a garden square.
-
D.
hasGardenCity
Indicates that an entity is associated with or contains a designated garden city.
-
E.
gardenAccess
Indicates that one entity is permitted to enter or use a particular garden area.
- 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_69ca82f749388190bffbea6dfb509016 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb810ac380819095bd67f0555ac2a8 |
completed | March 31, 2026, 8:08 a.m. |
| PD | Predicate disambiguation | batch_69cb70d24b248190a326aa6804f942b5 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:03 p.m.