Triple
T26443249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Detroit Fury |
E665143
|
entity |
| Predicate | arenaFootballLeagueFranchiseId |
P160759
|
FINISHED |
| Object | DET |
—
|
LITERAL FINISHED |
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: DET | Statement: [Detroit Fury, arenaFootballLeagueFranchiseId, DET]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: arenaFootballLeagueFranchiseId Context triple: [Detroit Fury, arenaFootballLeagueFranchiseId, DET]
-
A.
afcAffiliation
Indicates a formal association or membership relationship between an entity and an organization, group, or institution.
-
B.
americanFootballTeamOf
Indicates that one entity is the American football team associated with, representing, or belonging to another entity (such as a school, city, or organization).
-
C.
teamFranchise
Indicates that a sports team is associated with, or belongs to, a particular franchise organization.
-
D.
hostsSportsFranchise
Indicates that one entity serves as the home location or base city/venue for a professional sports franchise.
-
E.
NFLTeam
Indicates a relationship where an entity is identified as a professional American football team that competes in the National Football League.
- 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_69ee883c851881909e2ab04efbb3c5fe |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6121d00d48190b64b88a7d75c6e3b |
completed | May 2, 2026, 3:02 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69f604120e848190b516c29b781d19cc |
completed | May 2, 2026, 2:02 p.m. |
Created at: April 27, 2026, midnight