Triple
T27682535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lloydminster |
E697944
|
entity |
| Predicate | postalCodePrefixAlberta |
P961
|
FINISHED |
| Object | T9V |
—
|
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: T9V | Statement: [Lloydminster, postalCodePrefixAlberta, T9V]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postalCodePrefixAlberta Context triple: [Lloydminster, postalCodePrefixAlberta, T9V]
-
A.
routeNumberInAlberta
Indicates that a specified route or highway has a particular designated route number within the province of Alberta.
-
B.
postalCounty
Indicates the county associated with an entity for postal addressing or mail delivery purposes.
-
C.
postalArea
Indicates that one entity is the postal or ZIP code area associated with the location or address represented by the other entity.
-
D.
hasPostalAbbreviationProvince
Indicates that a province is associated with a specific standardized postal abbreviation used in mailing addresses.
-
E.
hasPostalCodePrefix
chosen
Indicates that a location’s postal code begins with a specified sequence of characters.
- 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_69ef590df8708190af5488f0638e790c |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6357044208190887c948836f44aee |
completed | May 2, 2026, 5:33 p.m. |
| PD | Predicate disambiguation | batch_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:47 p.m.