Triple
T16088758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Collection interiors at Windsor Castle |
E390302
|
entity |
| Predicate | formsPartOfTour |
P17534
|
FINISHED |
| Object | Windsor Castle visitor route |
—
|
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: Windsor Castle visitor route | Statement: [Royal Collection interiors at Windsor Castle, formsPartOfTour, Windsor Castle visitor route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsPartOfTour Context triple: [Royal Collection interiors at Windsor Castle, formsPartOfTour, Windsor Castle visitor route]
-
A.
tourWith
Indicates that one entity accompanies another on a tour, sharing the same itinerary or guided experience.
-
B.
tourOf
Indicates that one entity serves as a guided or organized visit through another entity, typically for exploration, education, or sightseeing.
-
C.
hasTour
Indicates that an entity offers, includes, or is associated with a tour experience or guided visit.
-
D.
hasTouristRoute
chosen
Indicates that a location or site is connected to or included in a designated tourist route or itinerary.
-
E.
subjectOfTour
Indicates that an entity serves as the main focus, destination, or theme of a tour.
- 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_69d87f198bc48190a8b7e53ca15b7ead |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e1827ad7c88190b867da511cbfb7fa |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:59 a.m.