Triple
T30366200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | India and Myanmar |
E772426
|
entity |
| Predicate | hasEthnicOverlap |
P115409
|
FINISHED |
| Object | Naga peoples |
—
|
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: Naga peoples | Statement: [India and Myanmar, hasEthnicOverlap, Naga peoples]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEthnicOverlap Context triple: [India and Myanmar, hasEthnicOverlap, Naga peoples]
-
A.
hasEthnicScope
Indicates that something is relevant or applicable specifically to a particular ethnic group or ethnic context.
-
B.
hasEthnicInfluence
Indicates that one entity has a cultural, traditional, or ethnic impact on, or contributes to shaping the ethnic character of, another entity.
-
C.
hasEthnicDivision
Indicates that a group, region, or entity is characterized by internal divisions or distinctions based on ethnicity.
-
D.
hasEthnolinguisticPresence
chosen
Indicates that a particular ethnolinguistic group is present or represented within a specified place, context, or population.
-
E.
hasEthnicallyMixedPopulation
Indicates that a population is composed of people from multiple distinct ethnic groups rather than being ethnically homogeneous.
- 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_69f2248d71408190aec0d5c2001b1cff |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 29, 2026, 7:58 p.m.