Triple
T31584565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azerbaijani Turks |
E805920
|
entity |
| Predicate | largestSubgroupOf |
P93814
|
FINISHED |
| Object | Turkic peoples |
—
|
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: Turkic peoples | Statement: [Azerbaijani Turks, largestSubgroupOf, Turkic peoples]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: largestSubgroupOf Context triple: [Azerbaijani Turks, largestSubgroupOf, Turkic peoples]
-
A.
revealedAsSubgroupOf
Indicates that one group has been newly identified or exposed as being a subgroup or subset of another group.
-
B.
areLargestGroupIn
Indicates that one group is the biggest or most numerous among all groups within a specified context or set.
-
C.
hasMaximalSubgroupOrder
Indicates that the subgroup in question has the greatest possible order (size) among all proper subgroups of the given group.
-
D.
isLargestSubfamilyOf
chosen
Indicates that one group or category is the largest subfamily within another, typically in terms of number of members or size.
-
E.
largestMemberOf
Indicates that an entity is the member of a group or set that has the greatest size, extent, or magnitude according to a specified measure.
- 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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a80c85748190b0cbf828e9c06b0d |
completed | May 3, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:25 p.m.