Triple
T31561387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nujiang Grand Canyon |
E805272
|
entity |
| Predicate | primaryEthnicGroupsNearby |
P65193
|
FINISHED |
| Object | Lisu people |
E730377
|
NE 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: Lisu people | Statement: [Nujiang Grand Canyon, primaryEthnicGroupsNearby, Lisu people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryEthnicGroupsNearby Context triple: [Nujiang Grand Canyon, primaryEthnicGroupsNearby, Lisu people]
-
A.
nearEthnicGroup
Indicates that one entity is located geographically close to an ethnic group.
-
B.
ethnicGroupLocatedIn
Indicates that a particular ethnic group is present, resides, or is primarily associated with a specific geographic location or region.
-
C.
dominantEthnicGroups
chosen
Indicates that the specified ethnic groups hold primary demographic, cultural, or political prominence within a given region or population.
-
D.
sharesEthnicity
Indicates that two entities belong to the same ethnic group or share the same ethnic background.
-
E.
relatedEthnicGroup
Indicates that there is a notable ethnic connection or association between two ethnic groups, such as shared ancestry, culture, or historical ties.
- F. None of above.
Provenance (4 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_69f348d22e088190ad555d5bd42f9da0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3729b8e0b08190a930e4d355b143f8 |
completed | June 21, 2026, midnight |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 10:15 p.m.