Triple
T28736769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tri-Cities |
E730821
|
entity |
| Predicate | hasPostalAbbreviationRegion |
P21657
|
FINISHED |
| Object | BC |
—
|
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: BC | Statement: [Tri-Cities, hasPostalAbbreviationRegion, BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPostalAbbreviationRegion Context triple: [Tri-Cities, hasPostalAbbreviationRegion, BC]
-
A.
hasPostalAbbreviationState
Indicates that a state is associated with a specific standardized postal abbreviation.
-
B.
hasPostalAbbreviationProvince
chosen
Indicates that a province is associated with a specific standardized postal abbreviation used in mailing addresses.
-
C.
hadPostalAbbreviation
Indicates that an entity was associated with a specific official postal abbreviation at some time.
-
D.
hasPostalQuadrantAbbreviation
Indicates that a postal address includes a specific quadrant abbreviation (such as NE, NW, SE, SW) as part of its location designation.
-
E.
areaAbbreviation
Indicates that one entity is an official abbreviated form or short code representing the named area of 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_69f043eae0908190b28ce314686247d7 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: April 28, 2026, 6:01 a.m.