Triple
T30775263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Republika Srpska |
E783645
|
entity |
| Predicate | callingCodeWithinBosniaAndHerzegovina |
P247
|
FINISHED |
| Object | +387 |
—
|
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: +387 | Statement: [Republika Srpska, callingCodeWithinBosniaAndHerzegovina, +387]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: callingCodeWithinBosniaAndHerzegovina Context triple: [Republika Srpska, callingCodeWithinBosniaAndHerzegovina, +387]
-
A.
callingCode
chosen
Indicates the telephone country or area code associated with an entity for making phone calls.
-
B.
callingCodeType
Indicates the type or category of a telephone calling code associated with an entity.
-
C.
telephoneDialingCodeSystem
Indicates the telephone numbering or dialing code scheme used to place calls within or to a particular region, network, or service.
-
D.
continentCode
Indicates the standardized code assigned to the continent with which an entity is associated.
-
E.
internationalCode
Indicates that there is a standardized internationally recognized code assigned to represent the referenced entity in global contexts.
- 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_69f224b1519081908b9db003fd2073e0 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68fe119788190afd49e20e189f3ef |
completed | May 2, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:40 p.m.