Triple
T22514899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian telephone numbering plan |
E556614
|
entity |
| Predicate | directoryEnquiryNumbersStartWith |
P148678
|
FINISHED |
| Object | 12 |
—
|
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: 12 | Statement: [Italian telephone numbering plan, directoryEnquiryNumbersStartWith, 12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directoryEnquiryNumbersStartWith Context triple: [Italian telephone numbering plan, directoryEnquiryNumbersStartWith, 12]
-
A.
numberOfNames
Indicates the count of distinct names associated with a given entity.
-
B.
directiveNumber
Indicates the identifying number assigned to a specific directive or formal instruction within a set of directives.
-
C.
fullNameIncludes
Indicates that one entity’s full name contains another specified string or name component as a substring.
-
D.
faitPartieDuRépertoire
Indicates that something is included within or belongs to a particular directory or repertoire.
-
E.
membersFoundIn
Indicates that the specified members are located within, contained in, or present in a particular group, collection, or context.
- 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_69e11e555edc81909ca803587dafd747 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15e2c3098819098a553133cc9515b |
completed | April 29, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69ee625e3b408190a60c759fb0b28fe2 |
completed | April 26, 2026, 7:07 p.m. |
| PDg | Predicate description generation | batch_69ee8841e9cc81908d23b34215e3be71 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 16, 2026, 8:50 p.m.