Triple
T18943250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MO |
E463440
|
entity |
| Predicate | relatedAbbreviationSystem |
P133893
|
FINISHED |
| Object | USPS state abbreviations |
—
|
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: USPS state abbreviations | Statement: [MO, relatedAbbreviationSystem, USPS state abbreviations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedAbbreviationSystem Context triple: [MO, relatedAbbreviationSystem, USPS state abbreviations]
-
A.
collaboratesWithAbbreviation
Indicates that one entity works jointly or cooperatively with another entity that is represented in abbreviated form.
-
B.
typeOfAbbreviation
Indicates that one term is an abbreviation of a specific type or category (e.g., acronym, initialism) of another expression.
-
C.
abbreviationOrShortForm
Indicates that one term is an abbreviation or shortened form of another term.
-
D.
sharesAbbreviationWith
Indicates that two entities use the same abbreviation or acronym to represent their names or designations.
-
E.
establishesAbbreviation
Indicates that one entity defines or introduces an abbreviated form that stands for another entity.
- F. None of above. chosen
Provenance (4 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_69d8dcfec90481909e926be9767e5779 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d3ed847c8190a911a61673608a5c |
completed | April 20, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69e4ad8e075c8190ad561edc5e520057 |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, 11:59 a.m.