Triple
T24916720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Banks riverfront district |
E624006
|
entity |
| Predicate | hasSportsTeamTenant |
P346
|
FINISHED |
| Object | Cincinnati Bengals |
—
|
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: Cincinnati Bengals | Statement: [The Banks riverfront district, hasSportsTeamTenant, Cincinnati Bengals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSportsTeamTenant Context triple: [The Banks riverfront district, hasSportsTeamTenant, Cincinnati Bengals]
-
A.
hasSportsTeam
Indicates that an entity possesses, sponsors, or is represented by a sports team.
-
B.
containsSportsTeam
chosen
Indicates that one entity (typically a location or organization) has a sports team as part of it or within its boundaries.
-
C.
hasAthleticTeamType
Indicates that an entity’s athletic team participates in or is classified under a specific type or category of sport or competition.
-
D.
sportsTeamTenancyStart
Indicates the date or point in time when an entity begins its occupancy or tenure as a sports team at a particular venue or location.
-
E.
sportsTeamPlaysIn
Indicates that a sports team regularly plays its home games or is based in a particular venue, city, or location.
- 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_69e2fac889c081908e9ff686cb428e5a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f60c3b09488190ade1b69ff7f0df0e |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 18, 2026, 5:28 a.m.