Triple
T9540086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poweshiek |
E230128
|
entity |
| Predicate | hasPartiallyNamedAfterIt |
P63
|
FINISHED |
| Object | Poweshiek County, 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: Poweshiek County, Iowa | Statement: [Poweshiek, hasPartiallyNamedAfterIt, Poweshiek County, Iowa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPartiallyNamedAfterIt Context triple: [Poweshiek, hasPartiallyNamedAfterIt, Poweshiek County, Iowa]
-
A.
usedAfterNameOf
Indicates that something is used immediately following the mention or specification of a name.
-
B.
namedAfter
chosen
Indicates that one entity has been given its name in honor of, or derived from, another entity.
-
C.
namedAfterSince
Indicates that one entity has borne the name of another entity starting from a specific point in time.
-
D.
laterNamed
Indicates that an entity was given a new name at a later time, linking its original identity to its subsequent name.
-
E.
hasSymbolNamedAfter
Indicates that one entity has a symbol whose name is derived from or dedicated to another entity.
- 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_69ca847b1b3081908f72bc932c17cc41 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd98e4df6c8190a4d1160c42daa45f |
completed | April 1, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69ccd58bd21881908b860e3ee469af13 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:01 p.m.