Triple
T27700117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Land Shark Stadium |
E698403
|
entity |
| Predicate | tenantLeagueDuringName |
P119447
|
FINISHED |
| Object | National Football League |
—
|
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: National Football League | Statement: [Land Shark Stadium, tenantLeagueDuringName, National Football League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tenantLeagueDuringName Context triple: [Land Shark Stadium, tenantLeagueDuringName, National Football League]
-
A.
tenantPlaysInLeague
chosen
Indicates that a tenant participates as a member or competitor in a particular league.
-
B.
tenantClubLeague
Indicates that a club participates as a tenant (home user of facilities) in a particular league.
-
C.
laterLeagueName
Indicates that an entity’s league name was changed to a different (later) league name at some point in time.
-
D.
locationLeague
Indicates that an entity (such as a sports team or club) is associated with or participates in a particular league.
-
E.
employerLeague
Indicates that an organization or entity serves as the employing league or governing competition body for another entity (such as a team or participant).
- 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_69ef590ea74081908f0cd7500d85fa27 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f635a29ff08190bfd246ccaf0ddb4e |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:56 p.m.