Triple
T21870523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toda |
E539987
|
entity |
| Predicate | sharesEthnicOriginWith |
P59955
|
FINISHED |
| Object | Seediq people |
—
|
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: Seediq people | Statement: [Toda, sharesEthnicOriginWith, Seediq people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesEthnicOriginWith Context triple: [Toda, sharesEthnicOriginWith, Seediq people]
-
A.
sharesEthnicity
chosen
Indicates that two entities belong to the same ethnic group or share the same ethnic background.
-
B.
sharesBorderWithEthnicGroup
Indicates that a geographic or political entity has a land or maritime boundary directly adjacent to the territory predominantly inhabited by a specified ethnic group.
-
C.
relatedEthnicGroup
Indicates that there is a notable ethnic connection or association between two ethnic groups, such as shared ancestry, culture, or historical ties.
-
D.
holderEthnicity
Indicates the ethnic background or group to which the holder of something (e.g., a document, account, or item) belongs.
-
E.
mayBelongToEthnicGroup
Indicates that an entity is possibly, but not certainly, a member of a specified ethnic group.
- 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_69e0c478f59081909d54302b57fc1ce3 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f0f33509d08190b33775abb84d5255 |
completed | April 28, 2026, 5:49 p.m. |
| PD | Predicate disambiguation | batch_69e6be9394f88190945ddd1dc004d29d |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:57 p.m.