Triple
T14431452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Château des Baux |
E357837
|
entity |
| Predicate | visitorAttractions |
P59374
|
FINISHED |
| Object | historical reenactments |
—
|
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: historical reenactments | Statement: [Château des Baux, visitorAttractions, historical reenactments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visitorAttractions Context triple: [Château des Baux, visitorAttractions, historical reenactments]
-
A.
relatedAttraction
Indicates that one attraction is associated with or connected to another attraction in some relevant way.
-
B.
attractionType
Indicates the specific kind or category of attraction that characterizes the relationship between entities.
-
C.
visitorAttractionSince
Indicates that an entity has served as a visitor attraction starting from a specified point in time.
-
D.
isMajorAttractionFor
Indicates that something serves as a primary or highly significant draw or point of interest for a particular audience, group, or location.
-
E.
offersAttraction
chosen
Indicates that one entity provides or presents an attraction, such as an activity, feature, or point of interest, to another entity or audience.
- 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_69d8279402a88190821ffa39ae15bccf |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de914570f08190b1c7c1c57a0cb476 |
completed | April 14, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69de5c30467881908e770e3940295641 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:18 a.m.