Triple
T30302894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fujian Tulou |
E770695
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | traditional rural settlement |
C22076
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: traditional rural settlement Context triple: [Fujian Tulou, instanceOf, traditional rural settlement]
-
A.
traditional village
chosen
A traditional village is a small, close-knit rural settlement characterized by long-established customs, locally sourced architecture, and community-based ways of life often centered around agriculture or artisanal trades.
-
B.
traditional homeland
A traditional homeland is a geographic area historically inhabited, used, and culturally identified with by an Indigenous or long-established community, forming the core of its ancestral identity and way of life.
-
C.
village-like settlement
A village-like settlement is a small, closely-knit residential community with limited infrastructure, where inhabitants live in close proximity and often share local resources, traditions, and social ties.
-
D.
Moravian settlement
A Moravian settlement is a planned religious community established by the Moravian Church, characterized by communal living, shared economic enterprises, and a strong emphasis on worship, education, and missionary work.
-
E.
rural town
A rural town is a small, sparsely populated community situated in the countryside, typically characterized by close-knit social ties, limited infrastructure, and an economy often based on agriculture or local resource industries.
- F. None of above.
Provenance (1 batch)
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_69f224881b948190b8c4921b250a44a3 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:49 p.m.