Triple
T31972920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jopadhola |
E816361
|
entity |
| Predicate | migrationRelation |
P36585
|
FINISHED |
| Object | part of wider Luo migrations |
—
|
LITERAL 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: part of wider Luo migrations | Statement: [Jopadhola, migrationRelation, part of wider Luo migrations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: migrationRelation Context triple: [Jopadhola, migrationRelation, part of wider Luo migrations]
-
A.
migrationLink
chosen
Indicates a relationship where one entity moves, transitions, or is transferred from one context, location, or system to another.
-
B.
foreignRelation
Indicates that there exists a diplomatic or international relationship between one entity and another entity from a different country or jurisdiction.
-
C.
cloneRelation
Indicates that one entity is a clone or exact copy derived from another entity.
-
D.
migrationPolicy
Indicates the rules or strategies governing how entities move, transfer, or transition from one context, location, or state to another.
-
E.
stageRelation
Indicates a relationship between entities based on their roles, positions, or phases within a staged process or sequence.
- 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_69f348f5ae5481909da0247869f51955 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b34303a88190b17cadc63ce00be3 |
completed | May 3, 2026, 2:30 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:10 a.m.