Triple
T26100464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mexican telephone numbering plan |
E658384
|
entity |
| Predicate | usesInternationalPrefix |
P110654
|
FINISHED |
| Object | 00 |
—
|
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: 00 | Statement: [Mexican telephone numbering plan, usesInternationalPrefix, 00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesInternationalPrefix Context triple: [Mexican telephone numbering plan, usesInternationalPrefix, 00]
-
A.
internationalPrefix
chosen
Indicates that one entity is the international dialing prefix used to place telephone calls from the other entity’s country to foreign destinations.
-
B.
usesForInternationalCode
Indicates that one entity employs another entity as its designated international code for identification or communication purposes.
-
C.
isInternational
Indicates that something has a connection to, involves, or extends across more than one country.
-
D.
isBroadcastInternationally
Indicates that a broadcast is transmitted and made available across multiple countries or beyond national boundaries.
-
E.
hasInternationalService
Indicates that an entity provides or is connected to transportation or communication services that operate across national borders.
- 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_69ee5bc09c288190bc42a11972841383 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 26, 2026, 7:54 p.m.