Triple
T578209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rum |
E15002
|
entity |
| Predicate | designatedAsNationalNatureReserve |
P3788
|
FINISHED |
| Object | 1957 |
—
|
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: 1957 | Statement: [Rum, designatedAsNationalNatureReserve, 1957]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designatedAsNationalNatureReserve Context triple: [Rum, designatedAsNationalNatureReserve, 1957]
-
A.
hasNatureDesignation
chosen
Indicates that something has been formally assigned a specific conservation, protection, or natural-area status or designation.
-
B.
hasUNESCOBiosphereReserve
Indicates that an entity includes, contains, or is associated with a designated UNESCO Biosphere Reserve.
-
C.
nationalPark
Indicates that a location is designated and managed as a national park by a governing authority.
-
D.
establishedAsNationalParkBy
Indicates that an area or site was officially designated and created as a national park through the action or authority of a specific person, organization, or governmental body.
-
E.
partOfProtectedAreaCategory
Indicates that one protected area belongs to, or is classified under, a specific protected area category.
- 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_69a4935783b8819082b77726ec10cc42 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49b69fed88190b5558d4ebd5047a1 |
completed | March 1, 2026, 8:02 p.m. |
| PD | Predicate disambiguation | batch_69a494c692288190b88f30299516b5ba |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.