Triple
T32280830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WA-02 |
E824683
|
entity |
| Predicate | usesPostalAbbreviationOfState |
P2461
|
FINISHED |
| Object | WA |
—
|
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: WA | Statement: [WA-02, usesPostalAbbreviationOfState, WA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPostalAbbreviationOfState Context triple: [WA-02, usesPostalAbbreviationOfState, WA]
-
A.
hasPostalAbbreviationState
chosen
Indicates that a state is associated with a specific standardized postal abbreviation.
-
B.
hadPostalAbbreviation
Indicates that an entity was associated with a specific official postal abbreviation at some time.
-
C.
hasPostalAbbreviationProvince
Indicates that a province is associated with a specific standardized postal abbreviation used in mailing addresses.
-
D.
postalStyleAbbreviation
Indicates that one term is a standardized shortened form of another term as used in postal addressing conventions.
-
E.
postalState
Indicates the state or province associated with an entity’s postal or mailing address.
- 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_69f3490f404081908450db66884f4334 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 1, 2026, 12:43 a.m.