Triple
T26677866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rock Island County |
E672513
|
entity |
| Predicate | locatedOnRiverIsland |
P156002
|
FINISHED |
| Object | Rock Island (island in Mississippi River) |
—
|
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: Rock Island (island in Mississippi River) | Statement: [Rock Island County, locatedOnRiverIsland, Rock Island (island in Mississippi River)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnRiverIsland Context triple: [Rock Island County, locatedOnRiverIsland, Rock Island (island in Mississippi River)]
-
A.
isOnRiverIsland
chosen
Indicates that one entity (typically a place or structure) is located on an island situated within a river.
-
B.
locatedOnIslandOfCountry
Indicates that something is situated on an island that belongs to, or is part of, a specified country.
-
C.
locatedOnBankOfRiver
Indicates that one entity is situated along or directly adjacent to the bank of a specified river.
-
D.
partOfIsland
Indicates that one entity is a portion or component of an island.
-
E.
locatedAcrossRiverFrom
Indicates that one entity is situated on the opposite side of a river relative 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_69eecda13424819092b17942c4edf722 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69fddd373cdc8190be1b12e70e4deb1f |
completed | May 8, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69fddc6915a88190ad41e379aa3ede13 |
completed | May 8, 2026, 12:51 p.m. |
Created at: April 27, 2026, 3:17 a.m.