Triple
T3116751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luang Prabang |
E65079
|
entity |
| Predicate | heritageAreaType |
P5929
|
FINISHED |
| Object | historic town |
—
|
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: historic town | Statement: [Luang Prabang, heritageAreaType, historic town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heritageAreaType Context triple: [Luang Prabang, heritageAreaType, historic town]
-
A.
heritageType
chosen
Indicates the classification of an entity’s cultural or natural heritage category or type within a heritage framework.
-
B.
heritageOrganizationType
Indicates the specific category or classification of a heritage-related organization in relation to its role or function.
-
C.
heritageField
Indicates that there is an association between an entity and a specific field, domain, or area related to cultural or historical heritage.
-
D.
historicAreaIncludes
Indicates that a designated historic area geographically contains or encompasses another place or feature within its boundaries.
-
E.
heritageSymbolOf
Indicates that something serves as a cultural or historical emblem representing the heritage or identity of a particular group, place, or tradition.
- 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_69ad857fcc088190b0c4d45a5cde6f61 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada4e5d1488190a2ab199625fdf05d |
completed | March 8, 2026, 4:33 p.m. |
| PD | Predicate disambiguation | batch_69ad9df455088190940ad04419772dc8 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:04 p.m.