Triple
T19304185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ukrainka |
E482777
|
entity |
| Predicate | telecommunicationCodeCountry |
P247
|
FINISHED |
| Object | +380 |
—
|
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: +380 | Statement: [Ukrainka, telecommunicationCodeCountry, +380]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: telecommunicationCodeCountry Context triple: [Ukrainka, telecommunicationCodeCountry, +380]
-
A.
continentCode
Indicates the standardized code assigned to the continent with which an entity is associated.
-
B.
callingCode
chosen
Indicates the telephone country or area code associated with an entity for making phone calls.
-
C.
internationalCode
Indicates that there is a standardized internationally recognized code assigned to represent the referenced entity in global contexts.
-
D.
countryCodeMeaning
Indicates the semantic meaning or description associated with a given country code.
-
E.
callingCodeType
Indicates the type or category of a telephone calling code associated with an 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_69d8e8d04d5c8190baa816986f2b1d1e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e604c5903c819090b3f89c3f33b005 |
completed | April 20, 2026, 10:49 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0bc7508190a6f9d56bd4c3404f |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:31 p.m.