Triple
T22428678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jatiluwih |
E554437
|
entity |
| Predicate | hasUNESCOCriterion |
P1725
|
FINISHED |
| Object | (iii) |
—
|
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: (iii) | Statement: [Jatiluwih, hasUNESCOCriterion, (iii)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUNESCOCriterion Context triple: [Jatiluwih, hasUNESCOCriterion, (iii)]
-
A.
UNESCOWorldHeritageCriteria
chosen
Indicates that a site meets one or more of the official UNESCO World Heritage criteria used to justify its inscription on the World Heritage List.
-
B.
hasUNESCOCandidateSite
Indicates that an entity possesses or includes at least one site that is a candidate for inscription on the UNESCO World Heritage List.
-
C.
unescoDesignation
Indicates that an entity has been granted a specific designation or status by UNESCO.
-
D.
culturalDesignation
Indicates that an entity has been assigned a particular cultural status, label, or classification within a specific cultural or heritage context.
-
E.
UNESCOSerialNomination
Indicates that multiple geographically or culturally related sites are jointly nominated as a single serial property on the UNESCO World Heritage List.
- 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_69e11e4f2d0c819091aa3558ea2ee630 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15a2f054c819093fbe173c8a4a544 |
completed | April 29, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69e898a327948190beee5e168006a0a7 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:47 p.m.