Triple
T9200755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burg Square |
E220830
|
entity |
| Predicate | isPartOfTourRoute |
P6309
|
FINISHED |
| Object | Bruges historic walking tours |
—
|
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: Bruges historic walking tours | Statement: [Burg Square, isPartOfTourRoute, Bruges historic walking tours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfTourRoute Context triple: [Burg Square, isPartOfTourRoute, Bruges historic walking tours]
-
A.
hasTouristRoute
Indicates that a location or site is connected to or included in a designated tourist route or itinerary.
-
B.
isPartOfRoute
chosen
Indicates that something (such as a segment, stop, or step) belongs to and is contained within a larger route.
-
C.
isPartOfTouristArea
Indicates that one entity is located within or belongs to a designated tourist area or tourist-focused region.
-
D.
isPartOfAttraction
Indicates that something is a component or sub-element within a larger attraction or point of interest.
-
E.
tourWith
Indicates that one entity accompanies another on a tour, sharing the same itinerary or guided experience.
- 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_69ca83e8e9248190862cf3e41693b310 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccd9429b448190a078e9cdfedd4918 |
completed | April 1, 2026, 8:37 a.m. |
| PD | Predicate disambiguation | batch_69cc660af2408190ae06eb8326e1c64e |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:25 p.m.