Triple
T30730734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 云梦县 |
E782413
|
entity |
| Predicate | telephonySystem |
P143537
|
FINISHED |
| Object | 中国大陆电话区号体系 |
—
|
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: 中国大陆电话区号体系 | Statement: [云梦县, telephonySystem, 中国大陆电话区号体系]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: telephonySystem Context triple: [云梦县, telephonySystem, 中国大陆电话区号体系]
-
A.
telecommunicationSystem
Indicates a relationship where communication between entities is carried out over a distance using electronic or digital transmission systems.
-
B.
callNumberSystem
Indicates a relationship where an entity uses or is organized according to a particular call number system for classification or identification.
-
C.
telephoneDialingCodeSystem
chosen
Indicates the telephone numbering or dialing code scheme used to place calls within or to a particular region, network, or service.
-
D.
telecommunicationsType
Indicates the specific category or mode of telecommunications service or technology associated with an entity.
-
E.
telecommunicationsProvider
Indicates that one entity provides telecommunications services (such as phone, internet, or data connectivity) to another entity.
- 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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68ee260ec81909d2da2ed8243ef2d |
completed | May 2, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:37 p.m.