Triple
T32162709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Redding |
E821468
|
entity |
| Predicate | hasAbbreviationForState |
P27729
|
FINISHED |
| Object | IA |
E79146
|
NE 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: IA | Statement: [Redding, hasAbbreviationForState, IA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAbbreviationForState Context triple: [Redding, hasAbbreviationForState, IA]
-
A.
hasPostalAbbreviationState
Indicates that a state is associated with a specific standardized postal abbreviation.
-
B.
hasAbbreviationForRegion
chosen
Indicates that one entity is used as the standard abbreviated form of the name of a particular region.
-
C.
areaAbbreviation
Indicates that one entity is an official abbreviated form or short code representing the named area of another entity.
-
D.
hasNameAbbreviation
Indicates that an entity is associated with a shortened or abbreviated form of its full name.
-
E.
hasAbbreviationStatus
Indicates that an entity has a particular status or condition regarding its abbreviation (e.g., whether it is abbreviated, how, or to what extent).
- F. None of above.
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_69f34905e098819082191a6922a6d607 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6ba1de3548190b51d38e380bc67ef |
completed | May 3, 2026, 2:59 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2f0bd27d80819092e258930938214b |
completed | June 14, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:33 a.m.