Triple
T34884684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Сокол (Красноярск) |
E1006110
|
entity |
| Predicate | homeRegionCountry |
P71281
|
FINISHED |
| Object | Россия |
—
|
NE NERFINISHED |
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: [Сокол (Красноярск), homeRegionCountry, Россия]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeRegionCountry Context triple: [Сокол (Красноярск), homeRegionCountry, Россия]
-
A.
homeCountryRegion
Indicates the country or broader geographic region that is considered the primary home or origin of an entity.
-
B.
homelandRegion
Indicates that a region is recognized as the native or traditional homeland of a particular entity (such as a people, group, or organization).
-
C.
countryOrRegion
Indicates that one entity is a country or geographic region associated with another entity (such as its location, jurisdiction, or area of relevance).
-
D.
regionOfHostCountry
chosen
Indicates that one entity is a geographic or administrative region belonging to, or located within, the specified host country.
-
E.
countryRegion
Indicates that a country is located within, or belongs to, a specific geographic or administrative region.
- 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_69f76dbedb288190afe5780710847410 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782f4f10081908f97f6d0d2dbeec7 |
completed | May 3, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69f780ff71cc8190a67e71076fbad81a |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.