Triple
T33197139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intha people |
E849796
|
entity |
| Predicate | traditionalDwellingLocation |
P112276
|
FINISHED |
| Object | Inle Lake |
—
|
NE NERFINISHED |
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: Inle Lake | Statement: [Intha people, traditionalDwellingLocation, Inle Lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalDwellingLocation Context triple: [Intha people, traditionalDwellingLocation, Inle Lake]
-
A.
traditionallyHouses
Indicates that one entity has historically or customarily served as the location or container for another entity.
-
B.
traditionalHousingRegion
Indicates the region where a group’s customary or historically established housing patterns are typically found.
-
C.
traditionallyResidesIn
chosen
Indicates that an entity customarily lives or has its long-established home in a particular place or region.
-
D.
regionOfHabitation
Indicates the geographic area or environment in which an entity typically lives or resides.
-
E.
traditionalLifestyleRegion
Indicates that a region is characterized by or associated with a traditional lifestyle or way of living.
- 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_69f3495efedc8190843a5728089544b9 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fed09a12648190affcd9bacf7ca275 |
completed | May 9, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69fecf91d6f481908deb60c965c433ed |
completed | May 9, 2026, 6:09 a.m. |
Created at: May 1, 2026, 1:29 a.m.