Triple
T38463829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toronto Defiant |
E912514
|
entity |
| Predicate | hasCompetitiveFormat |
P2673
|
FINISHED |
| Object | team-based FPS |
—
|
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: team-based FPS | Statement: [Toronto Defiant, hasCompetitiveFormat, team-based FPS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompetitiveFormat Context triple: [Toronto Defiant, hasCompetitiveFormat, team-based FPS]
-
A.
appliesToCompetitionFormat
Indicates that something is relevant or specifically designed for a particular competition format.
-
B.
competitionFormat
chosen
Indicates the specific structure or ruleset under which a competition is organized and conducted.
-
C.
competitionFoundedFormat
Indicates the type or structure of the format in which a competition was originally founded.
-
D.
hasBattleFormat
Indicates that an entity is associated with, or conducted under, a particular battle or combat ruleset or format.
-
E.
hasRaceFormat
Indicates that an entity is associated with, or characterized by, a particular race format or type of race structure.
- 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_69f76e861d8c81908559031dc66e3c15 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:31 p.m.