Triple
T28137804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ukrainian independence referendum, 1991 |
E714255
|
entity |
| Predicate | supportInAllRegions |
P122211
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Ukrainian independence referendum, 1991, supportInAllRegions, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportInAllRegions Context triple: [Ukrainian independence referendum, 1991, supportInAllRegions, yes]
-
A.
supportsRegion
Indicates that one entity provides assistance, resources, or backing to a specific geographic or administrative region.
-
B.
usedInAllRegionsOf
chosen
Indicates that something is utilized or applied in every region within a specified scope or system.
-
C.
internationalSupport
Indicates that one entity provides backing, assistance, or endorsement to another across national or international boundaries.
-
D.
supportsRegionRestriction
Indicates that an entity enforces or accommodates limitations on availability or access based on geographic regions.
-
E.
supportsCountry
Indicates that one entity provides assistance, endorsement, or backing to a specific country.
- 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_69efd6af156c81908f50c2cd7db0e1ef |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_6a006ef900148190ba52daf566882a03 |
completed | May 10, 2026, 11:41 a.m. |
| PD | Predicate disambiguation | batch_6a006c76ae748190bfe466d7d17d321e |
completed | May 10, 2026, 11:31 a.m. |
Created at: April 27, 2026, 9:51 p.m.