Triple
T1209364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khomanani Cultural Landscape |
E25963
|
entity |
| Predicate | hasHeritageCriteria |
P24666
|
FINISHED |
| Object | cultural |
—
|
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 | Statement: [Khomanani Cultural Landscape, hasHeritageCriteria, cultural]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeritageCriteria Context triple: [Khomanani Cultural Landscape, hasHeritageCriteria, cultural]
-
A.
hasHeritage
Indicates that an entity possesses or is associated with a particular cultural, ethnic, or ancestral background.
-
B.
hasHeritageOrganization
Indicates that an entity is associated with, or belongs to, a particular heritage-related organization.
-
C.
hasCulturalProperty
Indicates that something possesses or is associated with a cultural attribute, value, or characteristic.
-
D.
heritageStatus
Indicates that an entity holds a particular cultural, historical, or natural heritage designation or protection status.
-
E.
containsCulturalHeritageSite
Indicates that a place or area includes within its boundaries at least one recognized cultural heritage site.
- F. None of above. chosen
Provenance (4 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_69a4942b30f08190a91c60573e16b5ef |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bde30ce08190ab60a181ad2d321d |
completed | March 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6078088190ba0221ae3368416c |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bbf83584819088c69366f58586cc |
completed | March 1, 2026, 10:21 p.m. |
Created at: March 1, 2026, 7:46 p.m.