Triple
T32300126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Château de Chamerolles |
E825212
|
entity |
| Predicate | hasExhibitionRoute |
P185336
|
FINISHED |
| Object | scented walk through the castle |
—
|
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: scented walk through the castle | Statement: [Château de Chamerolles, hasExhibitionRoute, scented walk through the castle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExhibitionRoute Context triple: [Château de Chamerolles, hasExhibitionRoute, scented walk through the castle]
-
A.
hasExhibitionFunction
Indicates that an entity serves the role or purpose of exhibiting, displaying, or presenting something (e.g., objects, works, or information).
-
B.
hasExhibition
Indicates that an entity organizes, hosts, or presents a particular exhibition.
-
C.
hasExhibitionModel
Indicates that one entity serves as the exhibition or display model associated with another entity.
-
D.
hasExhibitionForm
Indicates that something is presented, displayed, or organized in a particular exhibition format or mode.
-
E.
hasExhibitionScope
Indicates the thematic, geographic, temporal, or conceptual range and boundaries that define what an exhibition covers.
- 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_69f349115304819084ee91d345b6c8aa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69f7be520f148190ba200bf3dbf40656 |
completed | May 3, 2026, 9:29 p.m. |
Created at: May 1, 2026, 12:45 a.m.