Triple
T31508471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Audience Chamber |
E803878
|
entity |
| Predicate | hasTourDescription |
P186473
|
FINISHED |
| Object | highlight of Linderhof Palace interior |
—
|
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: highlight of Linderhof Palace interior | Statement: [Audience Chamber, hasTourDescription, highlight of Linderhof Palace interior]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTourDescription Context triple: [Audience Chamber, hasTourDescription, highlight of Linderhof Palace interior]
-
A.
hasTour
Indicates that an entity offers, includes, or is associated with a tour experience or guided visit.
-
B.
tourDocumented
Indicates that a tour has been recorded or documented, typically capturing its details, events, or progression.
-
C.
hasTouristRoute
Indicates that a location or site is connected to or included in a designated tourist route or itinerary.
-
D.
tourComponentOf
Indicates that something functions as a constituent part or segment of a larger tour.
-
E.
isPartOfTourDocument
Indicates that a given document belongs to, or is included within, a specific tour-related collection or itinerary.
- 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_69f348ceb0a48190ae7feca263b6296c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f9fe1a1ca4819084c196f0041f0be2 |
completed | May 5, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69f9fd66eed48190bdc26a8def328c2d |
completed | May 5, 2026, 2:23 p.m. |
Created at: April 30, 2026, 9:48 p.m.