Triple
T17194362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | осетины |
E417308
|
entity |
| Predicate | этногенетическоеПроисхождение |
P51841
|
FINISHED |
| Object | иранские племена |
—
|
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: иранские племена | Statement: [осетины, этногенетическоеПроисхождение, иранские племена]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: этногенетическоеПроисхождение Context triple: [осетины, этногенетическоеПроисхождение, иранские племена]
-
A.
ethnogenesisOf
chosen
Indicates the process or relationship by which a particular group, culture, or people comes into existence or forms its distinct identity.
-
B.
ethnogenesisRegion
Indicates the geographic region where the formation or emergence of an ethnic group took place.
-
C.
ethnicOrigin
Indicates the relationship where an entity is associated with a particular ethnic group or ancestry.
-
D.
geneticOrigin
Indicates that one entity is the source or contributor of another entity’s genetic material or hereditary traits.
-
E.
ethnogenesisDebate
Indicates a scholarly or ideological dispute over how a particular ethnic group originated, formed, or came to be recognized.
- 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_69d886d6ba8c819093215917b3d01689 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42da93bf88190b60b658087779d36 |
completed | April 19, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69e383141ae0819096acd71683637cbc |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:38 a.m.