Triple
T2941948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morne Trois Pitons National Park |
E79406
|
entity |
| Predicate | yearOfInscription |
P963
|
FINISHED |
| Object | 1997 |
—
|
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: 1997 | Statement: [Morne Trois Pitons National Park, yearOfInscription, 1997]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOfInscription Context triple: [Morne Trois Pitons National Park, yearOfInscription, 1997]
-
A.
UNESCOWorldHeritageDesignationYear
chosen
Indicates the year in which a site was officially designated as a UNESCO World Heritage site.
-
B.
nationalHistoricLandmarkDesignationYear
Indicates the year in which an entity was officially designated as a National Historic Landmark.
-
C.
dateOfNationalMonumentDesignation
Indicates the specific date on which something was officially designated as a national monument.
-
D.
monumentProclamationYear
Indicates the year in which a monument was officially proclaimed or designated as such.
-
E.
UNESCOWorldHeritageExtensionYear
Indicates the year in which an existing UNESCO World Heritage Site was officially extended or had its boundaries/inscription scope modified.
- 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_69ad8b1089588190b74d9e2505e45762 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9870e5d08190b3b277ba823fe6a1 |
completed | March 8, 2026, 3:40 p.m. |
| PD | Predicate disambiguation | batch_69ad96088fb481909976b436c2b729d9 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:56 p.m.