Triple
T22680804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Novi dvor, Belgrade |
E560473
|
entity |
| Predicate | hasTourAccess |
P149219
|
FINISHED |
| Object | limited, by special arrangement or during events |
—
|
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: limited, by special arrangement or during events | Statement: [Novi dvor, Belgrade, hasTourAccess, limited, by special arrangement or during events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTourAccess Context triple: [Novi dvor, Belgrade, hasTourAccess, limited, by special arrangement or during events]
-
A.
hasTour
Indicates that an entity offers, includes, or is associated with a tour experience or guided visit.
-
B.
hasTourElement
Indicates that something includes or is associated with a specific element or component of a tour.
-
C.
hasTicketAccess
Indicates that an entity is permitted to view, use, or manage a particular ticket or set of tickets.
-
D.
hasTouringReputation
Indicates that an entity is recognized or reputed for its activities, performance, or presence while traveling or touring.
-
E.
hasTourHistoryWith
Indicates that two entities have previously participated together in one or more tours or touring events.
- 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_69e2454bfd00819099115715a22cb057 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1786027648190972d1b0bbe81ed13 |
completed | April 29, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69ee62a6245881909506ff502da14137 |
completed | April 26, 2026, 7:08 p.m. |
| PDg | Predicate description generation | batch_69ee8843d3308190b6e22bb98ae5c3d8 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:12 p.m.