Triple
T31069101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pearl of the Mississippi |
E791762
|
entity |
| Predicate | riverCityNickname |
P74834
|
FINISHED |
| Object | Muscatine, Iowa |
—
|
NE NERFINISHED |
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: Muscatine, Iowa | Statement: [Pearl of the Mississippi, riverCityNickname, Muscatine, Iowa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverCityNickname Context triple: [Pearl of the Mississippi, riverCityNickname, Muscatine, Iowa]
-
A.
cityNickname
Indicates that one entity is commonly used as an informal or alternative name for a city.
-
B.
cityNicknameAssociation
chosen
Indicates an associative relationship where a particular nickname is used to refer to or characterize a specific city.
-
C.
metropolitanAreaNickname
Indicates that a metropolitan area is known by a particular informal or colloquial nickname.
-
D.
isInCityNicknamed
Indicates that one entity is located in a city that is known by a particular nickname.
-
E.
cityNicknameOrigin
Indicates the relationship between a city and the source, reason, or inspiration from which its nickname is derived.
- 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_69f224cc0c5c81908404f087bff92997 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 29, 2026, 9:01 p.m.