Triple
T4213278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Talysh |
E93953
|
entity |
| Predicate | partOfLargerGroup |
P52847
|
FINISHED |
| Object | Iranian peoples |
—
|
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: Iranian peoples | Statement: [Talysh, partOfLargerGroup, Iranian peoples]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfLargerGroup Context triple: [Talysh, partOfLargerGroup, Iranian peoples]
-
A.
areLargestGroupIn
Indicates that one group is the biggest or most numerous among all groups within a specified context or set.
-
B.
partyComposition
Indicates how the members or elements of a group or party are arranged, distributed, or combined to form that party as a whole.
-
C.
consideredPartOf
chosen
Indicates that one entity is regarded or treated as a component, segment, or subset of another entity within a larger whole.
-
D.
areSometimesGroupedWith
Indicates that two or more entities are occasionally but not consistently classified, treated, or considered together as part of the same group.
-
E.
coveredGroup
Indicates that one group or set is included within, or has its members protected or accounted for by, another group or arrangement.
- 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_69b3451743608190808f41d17ccf2650 |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b34e098da881909a0cc339cc186627 |
completed | March 12, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69b347efd9b08190bb50f82e4e7fe06d |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:04 p.m.