Triple
T12261301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strachan, Kincardineshire, Scotland |
E292230
|
entity |
| Predicate | hasLocalDialCode |
P190
|
FINISHED |
| Object | 01330 |
—
|
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: 01330 | Statement: [Strachan, Kincardineshire, Scotland, hasLocalDialCode, 01330]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalDialCode Context triple: [Strachan, Kincardineshire, Scotland, hasLocalDialCode, 01330]
-
A.
hasIslandDialingCode
Indicates that an island is associated with a particular telephone dialing code used for placing calls to it.
-
B.
hasAreaCodeCountry
Indicates that a particular telephone area code is associated with or belongs to a specific country.
-
C.
isCountryCode
Indicates that one entity is a valid country code designating the country represented by the other entity.
-
D.
hasAreaCode
chosen
Indicates that a specified telephone area code is assigned to or associated with a particular geographic region, location, or phone service entity.
-
E.
callingCode
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_69d6ab6856488190b5d31178d5015f8e |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d9380a5e78819086bd4dfe9a83d1f5 |
completed | April 10, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69d91c4a66cc819083ce6fcaf5042af6 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:52 p.m.