Triple
T17194389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | осетины |
E417308
|
entity |
| Predicate | историческийПредок |
P126677
|
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.
historicalHeir
Indicates that one entity is recognized as the successor or inheritor of another in a historical or dynastic context.
-
B.
historicFor
Indicates that something holds historical significance or importance specifically in relation to another entity.
-
C.
historical
Indicates that the subject has existed, occurred, or been relevant in the past rather than in the present or future.
-
D.
historicallyIn
Indicates that one entity existed, occurred, or was situated within the historical context, period, or jurisdiction associated with another entity.
-
E.
historicalFate
Indicates that two entities share a common or interconnected outcome, destiny, or consequence within a historical context.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e39c2fedb881908bfed2c3e5f2616a |
completed | April 18, 2026, 2:58 p.m. |
Created at: April 10, 2026, 5:38 a.m.