Triple
T36558559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mien people |
E901760
|
entity |
| Predicate | diasporaCause |
P149419
|
FINISHED |
| Object | Indochina wars |
—
|
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: Indochina wars | Statement: [Mien people, diasporaCause, Indochina wars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: diasporaCause Context triple: [Mien people, diasporaCause, Indochina wars]
-
A.
diasporaDueTo
chosen
Indicates that a population has dispersed or migrated from its original homeland as a result of a specified cause or event.
-
B.
diasporaType
Indicates the specific kind or category of diaspora relationship that exists between a group and its place of origin.
-
C.
diasporaUse
Indicates that members of a diaspora community use, practice, or engage with something (e.g., a language, custom, or resource) in the context of their life outside their place of origin.
-
D.
diasporaComponentOf
Indicates that one entity is a constituent or subgroup of the broader diaspora associated with another entity.
-
E.
diasporaContext
Indicates that the relationship or action occurs within, is shaped by, or specifically concerns a diaspora setting or experience.
- 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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:11 p.m.