Triple
T32835617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iowa Hawkeyes swimming and diving |
E839819
|
entity |
| Predicate | homePoolLocation |
P102339
|
FINISHED |
| Object | University of Iowa campus |
—
|
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 campus | Statement: [Iowa Hawkeyes swimming and diving, homePoolLocation, University of Iowa campus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homePoolLocation Context triple: [Iowa Hawkeyes swimming and diving, homePoolLocation, University of Iowa campus]
-
A.
homePool
Indicates that an entity is associated with or belongs to a primary or default pool, typically used as its main or originating pool.
-
B.
homeWaterLocation
Indicates the typical body of water or water source associated with an entity’s home or primary habitat.
-
C.
hasSwimmingPool
Indicates that the subject possesses or includes a swimming pool as one of its features.
-
D.
poolLocation
chosen
Indicates that one entity is the physical location or site where a particular pool is situated.
-
E.
homeBaseOf
Indicates that a particular place serves as the primary location, headquarters, or main operational base for 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_69f3493ff0888190b51e974eae2a7834 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ce6d659881909ddcec1d2966e020 |
completed | May 3, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:16 a.m.