Triple
T33747700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tyari tribal communities |
E864742
|
entity |
| Predicate | collectiveNameVariant |
P172101
|
FINISHED |
| Object | Tyari tribe |
—
|
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: Tyari tribe | Statement: [Tyari tribal communities, collectiveNameVariant, Tyari tribe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectiveNameVariant Context triple: [Tyari tribal communities, collectiveNameVariant, Tyari tribe]
-
A.
collectivelyKnownAs
Indicates that multiple entities are referred to together under a single shared name or designation.
-
B.
collectiveNameForm
chosen
Indicates that one entity serves as the collective or group name form used to refer to multiple members of another entity or class.
-
C.
clanNameVariant
Indicates that one clan name is an alternative or variant form of another clan name.
-
D.
teamNameVariant
Indicates that one team name is an alternative or variant form of another team’s name.
-
E.
colonialNameVariant
Indicates that one name is a variant or alternative form of another that was used during a colonial period or in a colonial context.
- 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_69f3498c35f881909df279ae4270f831 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
Created at: May 1, 2026, 1:45 a.m.