Triple
T33786458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UB Stadium |
E865800
|
entity |
| Predicate | affiliationOfTenants |
P177686
|
FINISHED |
| Object | NCAA Division I FBS |
—
|
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: NCAA Division I FBS | Statement: [UB Stadium, affiliationOfTenants, NCAA Division I FBS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affiliationOfTenants Context triple: [UB Stadium, affiliationOfTenants, NCAA Division I FBS]
-
A.
anchorTenant
Indicates that an entity serves as a primary or major tenant whose presence helps attract other tenants or users to a shared space or platform.
-
B.
tenantsFrom
Indicates that one or more tenants originate from, are associated with, or are derived from a specified source entity.
-
C.
alsoTenant
Indicates that two or more entities share the status of being tenants, typically occupying the same property or rental arrangement.
-
D.
tenantsSupport
Indicates that one or more tenants provide backing, endorsement, or assistance to another entity or cause.
-
E.
alsoTenantFrom
Indicates that one entity is also a tenant originating from the same source, context, or provider as another entity.
- F. None of above. chosen
Provenance (4 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_69f3498ecc2c8190bcd85e3f11dc215e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: May 1, 2026, 1:45 a.m.