Triple
T5995383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indre-et-Loire |
E133453
|
entity |
| Predicate | hasUNESCOSiteType |
P7642
|
FINISHED |
| Object | cultural landscape |
—
|
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 landscape | Statement: [Indre-et-Loire, hasUNESCOSiteType, cultural landscape]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUNESCOSiteType Context triple: [Indre-et-Loire, hasUNESCOSiteType, cultural landscape]
-
A.
UNESCOSiteType
chosen
Indicates the classification of a UNESCO World Heritage Site according to its type (e.g., cultural, natural, or mixed).
-
B.
hasWorldHeritageSite
Indicates that a location or entity possesses or contains a site designated as a UNESCO World Heritage Site.
-
C.
UNESCOWorldHeritageSiteRelated
Indicates a relationship where one entity is designated as, part of, or otherwise officially associated with a UNESCO World Heritage Site.
-
D.
UNESCOWorldHeritageSiteWithin
Indicates that a UNESCO World Heritage Site is geographically located within the boundaries of a specified area or region.
-
E.
unescoDesignation
Indicates that an entity has been granted a specific designation or status by UNESCO.
- 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_69c00870ddbc81909880fa3864f4f38d |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04e943dcc8190a09817e8ef0e4188 |
completed | March 22, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69c049e152e88190979ab80cb9b50321 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:05 p.m.