Triple
T15294865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Longview |
E365626
|
entity |
| Predicate | hasDialingCodeCountry |
P247
|
FINISHED |
| Object | +44 |
—
|
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: +44 | Statement: [Longview, hasDialingCodeCountry, +44]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDialingCodeCountry Context triple: [Longview, hasDialingCodeCountry, +44]
-
A.
hasIslandDialingCode
Indicates that an island is associated with a particular telephone dialing code used for placing calls to it.
-
B.
continentCode
Indicates the standardized code assigned to the continent with which an entity is associated.
-
C.
hasAreaCodeCountry
Indicates that a particular telephone area code is associated with or belongs to a specific country.
-
D.
isCountryCode
Indicates that one entity is a valid country code designating the country represented by the other entity.
-
E.
callingCode
chosen
Indicates the telephone country or area code associated with an entity for making phone calls.
- 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_69d85a103d9081908c1ea6c4c73ac8e3 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03682ea488190ac82fdbd0e855d34 |
completed | April 16, 2026, 1:08 a.m. |
| PD | Predicate disambiguation | batch_69deca935e2c8190b640987ddfc542b9 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:15 a.m.