Triple
T34549714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santa Cruz de Bezana |
E887027
|
entity |
| Predicate | usesRegionalDialingCode |
P156800
|
FINISHED |
| Object | 942 |
—
|
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: 942 | Statement: [Santa Cruz de Bezana, usesRegionalDialingCode, 942]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRegionalDialingCode Context triple: [Santa Cruz de Bezana, usesRegionalDialingCode, 942]
-
A.
hasIslandDialingCode
Indicates that an island is associated with a particular telephone dialing code used for placing calls to it.
-
B.
nationalPrefixForDomesticCalls
Indicates the dialing prefix that must be used when making domestic telephone calls within a given country or numbering plan.
-
C.
regionCodeUsedIn
chosen
Indicates that a specific region code is utilized or applied within a particular context, system, or entity.
-
D.
requiresAreaCodeForLocalCalls
Indicates that making local telephone calls in the given context necessitates dialing the area code.
-
E.
usesVariableLengthAreaCodes
Indicates that the telephone numbering plan in question employs area codes whose lengths are not fixed but can vary.
- 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_69f349cff89081908f91e0b064f4833e |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 1, 2026, 2:02 a.m.