Triple
T24012229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Champions Indoor Football 2016 season |
E594563
|
entity |
| Predicate | usesTeamFranchises |
P154858
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Champions Indoor Football 2016 season, usesTeamFranchises, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTeamFranchises Context triple: [Champions Indoor Football 2016 season, usesTeamFranchises, yes]
-
A.
teamFranchise
Indicates that a sports team is associated with, or belongs to, a particular franchise organization.
-
B.
team2Franchise
Indicates a relationship where a second team is associated with, or belongs to, a particular franchise.
-
C.
team1Franchise
Indicates that an entity serves as or represents the franchise associated with the first team in a given sports or competitive context.
-
D.
playsForFranchise
Indicates that one entity is an athlete or performer who is a member of, or competes on behalf of, a particular sports franchise or team.
-
E.
hostTeamFranchise
Indicates that a team franchise is serving as the host team in a given game or event.
- 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_69e288bc8f608190ac4af29f0bd1c744 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d59d6a2c8190860a44c056030826 |
completed | April 29, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
| PDg | Predicate description generation | batch_69f17c28b684819084eea522126463f8 |
completed | April 29, 2026, 3:34 a.m. |
Created at: April 17, 2026, 9:41 p.m.