Triple
T8838407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Pantheon |
E210324
|
entity |
| Predicate | hasTouristicUse |
P33155
|
FINISHED |
| Object | cultural tourism attraction |
—
|
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: cultural tourism attraction | Statement: [Royal Pantheon, hasTouristicUse, cultural tourism attraction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTouristicUse Context triple: [Royal Pantheon, hasTouristicUse, cultural tourism attraction]
-
A.
hasTourismFunction
chosen
Indicates that an entity serves a role or purpose related to tourism, such as attracting, accommodating, or providing services to tourists.
-
B.
hasTourismStyle
Indicates the type or style of tourism associated with or characteristic of a particular entity.
-
C.
hasTouristInfrastructure
Indicates that a place is equipped with facilities and services designed to support and accommodate tourists.
-
D.
isPartOfTouristArea
Indicates that one entity is located within or belongs to a designated tourist area or tourist-focused region.
-
E.
hasTourismResource
Indicates that a place, area, or entity possesses or is associated with a tourism-related resource, attraction, or facility.
- 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_69ca8388549c819095fd94eadefbb007 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc606c60ac8190b2b6bd7f042c02f8 |
completed | April 1, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69cc5c25b874819084c9ba391703e066 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:48 p.m.