Triple
T24686973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Ossetian ASSR |
E611323
|
entity |
| Predicate | elevatedToASSR |
P3787
|
FINISHED |
| Object | 1936 |
—
|
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: 1936 | Statement: [North Ossetian ASSR, elevatedToASSR, 1936]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevatedToASSR Context triple: [North Ossetian ASSR, elevatedToASSR, 1936]
-
A.
elevatedTo
chosen
Indicates that one entity is promoted or raised to a higher rank, status, position, or level relative to another.
-
B.
reconstructedAsElevated
Indicates that something has been rebuilt, modeled, or interpreted as having a higher or raised position relative to its original or surrounding context.
-
C.
soundAmplification
Indicates that one entity increases the loudness or intensity of another entity’s sound.
-
D.
elevatedFeature
Indicates that one feature or element is positioned or raised higher relative to another reference level or surrounding context.
-
E.
usesAudioFrom
Indicates that one entity incorporates or relies on the audio content produced or provided by 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_69e2c4d678b081908910f4271627a31a |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442a977b08190b44eac040cb90211 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 3:19 a.m.