Triple
T28832478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honghe Hani Rice Terraces |
E728086
|
entity |
| Predicate | includesVillageType |
P4011
|
FINISHED |
| Object | Hani traditional villages |
—
|
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: Hani traditional villages | Statement: [Honghe Hani Rice Terraces, includesVillageType, Hani traditional villages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesVillageType Context triple: [Honghe Hani Rice Terraces, includesVillageType, Hani traditional villages]
-
A.
isVillage
Indicates that the subject entity is classified as a village, typically a small human settlement or community.
-
B.
excludesVillage
Indicates that one entity explicitly omits, leaves out, or does not include the other entity in a specified village-related context.
-
C.
hasVillage
chosen
Indicates that an entity possesses, contains, or is associated with a village.
-
D.
hasCraftVillageType
Indicates that an entity is associated with, or classified by, a specific type or category of craft village.
-
E.
isVillageDistrictOf
Indicates that one administrative unit is a village-level district that belongs to or is governed by a larger territorial entity.
- 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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69ff46afe7e481908f2862ed11c88db2 |
completed | May 9, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69ff45e9151881909c444a655e852165 |
completed | May 9, 2026, 2:34 p.m. |
Created at: April 28, 2026, 6:38 a.m.