Triple
T26877466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ертіс |
E676789
|
entity |
| Predicate | hasInternationalImportance |
P191339
|
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: [Ертіс, hasInternationalImportance, так]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInternationalImportance Context triple: [Ертіс, hasInternationalImportance, так]
-
A.
continentalImportance
Indicates the degree to which something is significant or influential at the scale of an entire continent.
-
B.
hasNationalImportance
Indicates that something possesses significance or relevance at the level of an entire nation, rather than just local or regional importance.
-
C.
hasCommercialImportance
Indicates that something possesses economic or business value significant enough to impact trade, revenue, or market activity.
-
D.
hasStrategicImportanceType
Indicates that something is classified according to a specific category or type of strategic importance.
-
E.
hasJurisdictionalImportance
Indicates that something holds significant relevance or influence within a particular legal or administrative jurisdiction.
- F. None of above. chosen
Provenance (4 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_69eee9bb44988190b6e11652d028bc59 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
| PDg | Predicate description generation | batch_69fcdf22ab8881908b257f16522920c5 |
completed | May 7, 2026, 6:51 p.m. |
Created at: April 27, 2026, 5:36 a.m.