Triple
T16223845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wallenstein Palace |
E393793
|
entity |
| Predicate | hasGardenAccess |
P80770
|
FINISHED |
| Object | accessible from Letenská Street |
—
|
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: accessible from Letenská Street | Statement: [Wallenstein Palace, hasGardenAccess, accessible from Letenská Street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGardenAccess Context triple: [Wallenstein Palace, hasGardenAccess, accessible from Letenská Street]
-
A.
gardenAccess
chosen
Indicates that one entity is permitted to enter or use a particular garden area.
-
B.
hasGardenType
Indicates that an entity possesses or is associated with a garden of a specified type.
-
C.
containsGarden
Indicates that one entity includes or has a garden within its area or boundaries.
-
D.
hasGardenSquare
Indicates that an entity includes, is adjacent to, or is otherwise associated with a garden square.
-
E.
hasGardenRelation
Indicates a relationship in which one entity is associated with another through the presence, ownership, or inclusion of a garden.
- 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_69d87f204df88190a8f88923decf9835 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e23d23e63881908806920d878f2adb |
completed | April 17, 2026, 2:01 p.m. |
| PD | Predicate disambiguation | batch_69e219e94a448190b73a4e6aa374eb4a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.