Triple
T30336860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UrFO |
E771645
|
entity |
| Predicate | hasRussianAbbreviation |
P8075
|
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: [UrFO, hasRussianAbbreviation, УрФО]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRussianAbbreviation Context triple: [UrFO, hasRussianAbbreviation, УрФО]
-
A.
hasRussianVersion
Indicates that something has a corresponding version or counterpart that is in the Russian language.
-
B.
hasFinnishAbbreviation
Indicates that one entity is the standard Finnish-language abbreviation or shortened form of another entity.
-
C.
hasNameAbbreviation
chosen
Indicates that an entity is associated with a shortened or abbreviated form of its full name.
-
D.
hasCountryAbbreviation
Indicates that an entity is associated with a specific standardized abbreviated form of a country’s name.
-
E.
hasAbbreviationStatus
Indicates that an entity has a particular status or condition regarding its abbreviation (e.g., whether it is abbreviated, how, or to what extent).
- 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_69f2248aba24819095bb86480d55b23b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 29, 2026, 7:54 p.m.