Triple
T38094748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schönbrunn Palace Gardens |
E951212
|
entity |
| Predicate | admissionToMainGardens |
P153728
|
FINISHED |
| Object | free |
—
|
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: free | Statement: [Schönbrunn Palace Gardens, admissionToMainGardens, free]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: admissionToMainGardens Context triple: [Schönbrunn Palace Gardens, admissionToMainGardens, free]
-
A.
isEntranceThemeOf
Indicates that a particular musical piece or motif serves as the entrance theme associated with a specific entity (such as a character, performer, or event).
-
B.
hasLandmarkAtEntrance
Indicates that a specific landmark is located at or directly adjacent to the entrance of something.
-
C.
isMainEntrance
Indicates that an entrance serves as the primary or principal access point to a place or building.
-
D.
hasAttractionAccess
chosen
Indicates that an entity has permission or the ability to enter, use, or benefit from a specified attraction.
-
E.
guardedEntranceTo
Indicates that one entity serves as a protective or controlling barrier for access to another entity’s entrance.
- 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_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.