Triple
T14233944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USPS state and territory abbreviation system |
E352824
|
entity |
| Predicate | formatConstraint |
P58313
|
FINISHED |
| Object | two uppercase letters |
—
|
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: two uppercase letters | Statement: [USPS state and territory abbreviation system, formatConstraint, two uppercase letters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formatConstraint Context triple: [USPS state and territory abbreviation system, formatConstraint, two uppercase letters]
-
A.
formatRequirement
Indicates that one entity specifies the required structure, style, or arrangement that another entity must follow or conform to.
-
B.
hasFormalConstraint
chosen
Indicates that an entity is governed or restricted by an explicitly defined formal rule, condition, or limitation.
-
C.
formatMayChange
Indicates that the format or structure of something is subject to modification and may not remain consistent over time.
-
D.
format
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
-
E.
meetsFormat
Indicates that something conforms to, satisfies, or is compliant with a specified format or structural standard.
- 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_69d8278adc7c8190a9218d69bce3c4e6 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de62411c888190a154acd56fe3fcaf |
completed | April 14, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69de05bf069c8190b69f00f00f5eb126 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:07 a.m.