Triple
T32198593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint-Martin-de-Ré |
E822465
|
entity |
| Predicate | hasUNESCOStatusSince |
P57323
|
FINISHED |
| Object | 2008 |
—
|
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: 2008 | Statement: [Saint-Martin-de-Ré, hasUNESCOStatusSince, 2008]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUNESCOStatusSince Context triple: [Saint-Martin-de-Ré, hasUNESCOStatusSince, 2008]
-
A.
yearOfUNESCORecognition
Indicates the specific year in which something was officially recognized or inscribed by UNESCO.
-
B.
inscribedOnUNESCOListInYear
chosen
Indicates that an entity was officially added to a UNESCO list (such as World Heritage) in a specified year.
-
C.
UNESCOInscribedBy
Indicates that a site, object, or element has been formally inscribed or designated by UNESCO, typically on one of its official heritage or recognition lists.
-
D.
hasUNESCOCandidateSite
Indicates that an entity possesses or includes at least one site that is a candidate for inscription on the UNESCO World Heritage List.
-
E.
UNESCOWorldHeritageDesignationYear
Indicates the year in which a site was officially designated as a UNESCO World Heritage site.
- 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_69f349093174819086e633c190a51aa8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 1, 2026, 12:36 a.m.