Triple
T31552254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICR Corridor |
E805035
|
entity |
| Predicate | hasAnchorInstitution |
P64535
|
FINISHED |
| Object | University of 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: University of Iowa | Statement: [ICR Corridor, hasAnchorInstitution, University of Iowa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAnchorInstitution Context triple: [ICR Corridor, hasAnchorInstitution, University of Iowa]
-
A.
hasFinancialInstitution
Indicates that one entity is associated with or linked to a financial institution, such as a bank or similar financial service provider.
-
B.
hasBankOn
Indicates that one entity is located on or alongside the bank (edge) of another entity, typically a river, lake, or similar body.
-
C.
hasBank
Indicates that one entity possesses, is associated with, or is served by a particular bank (such as a financial institution or river bank).
-
D.
hasAnchorStores
Indicates that a retail property or shopping center includes one or more major anchor stores as primary tenants.
-
E.
hasInstitutions
chosen
Indicates that one entity possesses, contains, or is associated with one or more institutions.
- 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_69f348d22e088190ad555d5bd42f9da0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: April 30, 2026, 10:11 p.m.