Triple
T35178537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pianiga |
E1015780
|
entity |
| Predicate | telephonePrefixType |
P182088
|
FINISHED |
| Object | area code |
—
|
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: area code | Statement: [Pianiga, telephonePrefixType, area code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: telephonePrefixType Context triple: [Pianiga, telephonePrefixType, area code]
-
A.
nationalPrefixForDomesticCalls
Indicates the dialing prefix that must be used when making domestic telephone calls within a given country or numbering plan.
-
B.
callingCodeType
Indicates the type or category of a telephone calling code associated with an entity.
-
C.
mobileNumberPrefix
chosen
Indicates that one entity is a telephone number prefix associated with, or used to begin, the other entity’s mobile phone numbers.
-
D.
telephoneAccessNumberType
Indicates the classification or category of a telephone access number, such as the type of service or access method it represents.
-
E.
telephoneStandard
Indicates that there is a relationship involving the use of a particular telephone standard or protocol for communication between entities.
- 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_69f76ddcc108819097f96853b7ed9ef4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78d78d7c8819081e37e0881eafd91 |
completed | May 3, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f78b9106008190930b3b3675b737d6 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:02 p.m.