Triple
T19747438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | area code 234 |
E474288
|
entity |
| Predicate | telephoneNumberFormat |
P132629
|
FINISHED |
| Object | +1 234 NXX XXXX |
—
|
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: +1 234 NXX XXXX | Statement: [area code 234, telephoneNumberFormat, +1 234 NXX XXXX]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: telephoneNumberFormat Context triple: [area code 234, telephoneNumberFormat, +1 234 NXX XXXX]
-
A.
countryCodeFormat
Indicates the standardized structure or pattern in which a country's code must be represented.
-
B.
telephoneStandard
Indicates that there is a relationship involving the use of a particular telephone standard or protocol for communication between entities.
-
C.
internationalFormat
chosen
Indicates that a value is expressed using a standardized international representation or notation, rather than a local or regional format.
-
D.
telephoneNumberingPlan
Indicates a relationship where a telephone numbering plan defines or governs how telephone numbers are structured, assigned, or managed for a given telecommunication context.
-
E.
identificationNumberFormat
Indicates the specific structural pattern or rules that an identification number must follow.
- 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_69d8e51940a0819087bd2996f98da668 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65295f3b88190a541354f41e3ea1d |
completed | April 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69e5305016e08190b9561a96baecb0b8 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:47 p.m.