Triple
T1048597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TW |
E22640
|
entity |
| Predicate | hasRelatedTelephoneCountryCode |
P247
|
FINISHED |
| Object | +886 |
—
|
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: +886 | Statement: [TW, hasRelatedTelephoneCountryCode, +886]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelatedTelephoneCountryCode Context triple: [TW, hasRelatedTelephoneCountryCode, +886]
-
A.
callingCode
chosen
Indicates the telephone country or area code associated with an entity for making phone calls.
-
B.
associatedNumber
Indicates a relationship where a specific number is linked or assigned to an entity as its associated value.
-
C.
callingCodeType
Indicates the type or category of a telephone calling code associated with an entity.
-
D.
hasAreaCodeType
Indicates that an entity’s area code is associated with a specific type or classification of area code.
-
E.
hasPostalCountryCode
Indicates that an entity is associated with a specific country code used for postal addressing or mail routing.
- 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_69a493da02e081908c13ff5e02a0fe7a |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b8f28c7c8190b9ca3749666bcbf3 |
completed | March 1, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69a4b72e3e488190b768005ad647886b |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.