Triple
T16732225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North American Numbering Plan |
E406618
|
entity |
| Predicate | includesSpecialServiceCodes |
P124428
|
FINISHED |
| Object | 800 |
—
|
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: 800 | Statement: [North American Numbering Plan, includesSpecialServiceCodes, 800]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesSpecialServiceCodes Context triple: [North American Numbering Plan, includesSpecialServiceCodes, 800]
-
A.
includesServiceFor
Indicates that one entity’s offering or package contains or covers a particular service provided for another entity.
-
B.
hasSpecials
Indicates that an entity offers or is associated with special deals, promotions, or limited-time offers.
-
C.
hasSpecialProcedure
Indicates that a particular entity is associated with or governed by a designated special procedure or process.
-
D.
hasSpecial
Indicates that an entity possesses or is associated with a distinctive or exceptional attribute, status, or feature compared to others.
-
E.
hasNumberOfSpecials
Indicates that an entity is associated with a specific count of special items, features, or occurrences.
- F. None of above. chosen
Provenance (4 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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e39c362bb88190921fab43d76c3ee8 |
completed | April 18, 2026, 2:59 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
| PDg | Predicate description generation | batch_69e326b9e84881909a9166e65bd850d6 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:20 a.m.