Triple
T8393122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Русины |
E197989
|
entity |
| Predicate | историческоеСамоназвание |
P28982
|
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.
historicalNameType
Indicates that the relationship specifies the type or category of a historical name associated with an entity.
-
B.
historical
Indicates that the subject has existed, occurred, or been relevant in the past rather than in the present or future.
-
C.
regionHistoricalName
chosen
Indicates that a region has been known by a particular historical name during some past period.
-
D.
historicalOrigin
Indicates the relationship by which one entity serves as the source, origin, or starting point in history for another entity.
-
E.
historicallyIn
Indicates that one entity existed, occurred, or was situated within the historical context, period, or jurisdiction associated with another entity.
- 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_69ca82f816bc8190ab321c07d72208c1 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb8184788081909e9857afff629985 |
completed | March 31, 2026, 8:10 a.m. |
| PD | Predicate disambiguation | batch_69cb70d24b248190a326aa6804f942b5 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:03 p.m.