Triple
T28631325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lansing, Iowa |
E724645
|
entity |
| Predicate | bridgeCrossesAt |
P106621
|
FINISHED |
| Object | Black Hawk Bridge over Mississippi River |
—
|
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: Black Hawk Bridge over Mississippi River | Statement: [Lansing, Iowa, bridgeCrossesAt, Black Hawk Bridge over Mississippi River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bridgeCrossesAt Context triple: [Lansing, Iowa, bridgeCrossesAt, Black Hawk Bridge over Mississippi River]
-
A.
bridgeLocation
Indicates the specific place or area where a bridge is situated or spans.
-
B.
hasBridgeTypeCrossing
Indicates that a bridge is characterized by a specific type of crossing it provides or supports.
-
C.
hasBridgeCrossings
chosen
Indicates that one entity has one or more bridge structures that span across or connect over another entity (such as a road, river, or area).
-
D.
riverCrossingStructure
Indicates a structure that allows passage across a river, such as by spanning or traversing it.
-
E.
bridgeType
Indicates the specific kind or classification of a bridge associated with an 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_69f01d8328c48190bc0e5f9b9b848582 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:37 a.m.