Triple
T34737286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phu Xuyen District |
E1001381
|
entity |
| Predicate | hasTraditionalVillageType |
P37515
|
FINISHED |
| Object | woodworking 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: woodworking villages | Statement: [Phu Xuyen District, hasTraditionalVillageType, woodworking villages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalVillageType Context triple: [Phu Xuyen District, hasTraditionalVillageType, woodworking villages]
-
A.
hasTraditionalSettlementType
Indicates that an entity is associated with a specific traditional or historically established type of human settlement (e.g., village, town, hamlet).
-
B.
hasNearbyTraditionalVillage
Indicates that an entity is located close to or in the vicinity of a traditional village.
-
C.
hasCraftVillageType
chosen
Indicates that an entity is associated with, or classified by, a specific type or category of craft village.
-
D.
hasVillage
Indicates that an entity possesses, contains, or is associated with a village.
-
E.
isAncestralVillageOf
Indicates that one place is the original home or traditional village from which another person, family, or community traces its ancestry.
- 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_69f76daf739881909ed3554f98a2b433 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ff84df768c81908c65a1a7e33103ad |
completed | May 9, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69ff848d0af881908ee42c27a58af47e |
completed | May 9, 2026, 7:01 p.m. |
Created at: May 3, 2026, 3:59 p.m.