Triple
T33658502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leiria Castle |
E862285
|
entity |
| Predicate | hasTouristImportance |
P34399
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Leiria Castle, hasTouristImportance, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTouristImportance Context triple: [Leiria Castle, hasTouristImportance, high]
-
A.
hasTouristAttractionRole
Indicates that an entity serves in the capacity or function of a tourist attraction for another entity (such as a place, organization, or area).
-
B.
isTouristDestination
Indicates that a place is recognized as a location people commonly visit for leisure, sightseeing, or travel.
-
C.
hasGoalForTourists
Indicates that something is intended or designed to achieve a specific objective or benefit for tourists.
-
D.
hasTouristRank
chosen
Indicates that an entity is assigned a specific rank or rating based on its attractiveness or importance as a tourist destination.
-
E.
hasTouristInfrastructure
Indicates that a place is equipped with facilities and services designed to support and accommodate tourists.
- 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_69f349840ba881908e3bfce536aeb92b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: May 1, 2026, 1:42 a.m.