Triple
T21157998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IN-2 |
E521361
|
entity |
| Predicate | usesAbbreviationStyle |
P24474
|
FINISHED |
| Object | postal-style abbreviation |
—
|
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: postal-style abbreviation | Statement: [IN-2, usesAbbreviationStyle, postal-style abbreviation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesAbbreviationStyle Context triple: [IN-2, usesAbbreviationStyle, postal-style abbreviation]
-
A.
usesAbbreviationIn
Indicates that an entity is referred to by an abbreviated form within a specified context, source, or representation.
-
B.
hasAbbreviationStyleName
Indicates that an entity is associated with a specific style or form of its abbreviated name.
-
C.
abbreviationStyle
chosen
Indicates the specific way in which something is abbreviated, such as the format, punctuation, or capitalization used in its shortened form.
-
D.
usesAbbreviationInStatistics
Indicates that one entity employs an abbreviated form of another entity specifically within statistical contexts or analyses.
-
E.
isAbbreviation
Indicates that one term is a shortened or abbreviated form of another term.
- 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_69e0b50d1ea481909c07e63c3ead9316 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7252dc3f0819094c6acf52a9f308d |
completed | April 21, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f5f8a5bc819081918c7fa8e4496d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:59 p.m.