Triple
T12763174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Optimum Voice |
E305045
|
entity |
| Predicate | numberPortability |
P15690
|
FINISHED |
| Object | supports number porting from other carriers |
—
|
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: supports number porting from other carriers | Statement: [Optimum Voice, numberPortability, supports number porting from other carriers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberPortability Context triple: [Optimum Voice, numberPortability, supports number porting from other carriers]
-
A.
supportsNumberPorting
chosen
Indicates that an entity enables or allows the transfer of an existing phone number from one service or provider to another.
-
B.
telecommunicationsProvider
Indicates that one entity provides telecommunications services (such as phone, internet, or data connectivity) to another entity.
-
C.
numberRetiredNumber
Indicates that a specific jersey number has been officially retired in honor of a particular person or entity.
-
D.
networkOperatorMCC_MNC
Indicates that a specific mobile network operator is identified by the given combination of Mobile Country Code (MCC) and Mobile Network Code (MNC).
-
E.
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.
- 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_69d7bdf1fcd081909ffb0e0d6fa3a07d |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d8f9f588190bffdea878856204b |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96409739881909174ba005a986cb5 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:28 p.m.