Triple
T24469354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FTC World Championship |
E617056
|
entity |
| Predicate | usesGameFormat |
P101458
|
FINISHED |
| Object | annual FTC game challenge |
—
|
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: annual FTC game challenge | Statement: [FTC World Championship, usesGameFormat, annual FTC game challenge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesGameFormat Context triple: [FTC World Championship, usesGameFormat, annual FTC game challenge]
-
A.
hasPlayFormat
chosen
Indicates that something (such as a game, media, or activity) is associated with a particular format or mode in which it is played or experienced.
-
B.
supportsGames
Indicates that an entity is capable of running, handling, or being compatible with one or more games.
-
C.
includesGameType
Indicates that one entity contains or supports a particular type or category of game.
-
D.
hasGameSystem
Indicates that an item, product, or context is associated with or supports a particular game system or rules framework.
-
E.
hasGameType
Indicates that an entity (such as a game or match) is associated with a specific category or type of game.
- 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_69e2d7f197588190889a03e620558059 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f299422cdc8190bc8d56243b7bc313 |
completed | April 29, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69f287d76c7c81909494f12e606a9149 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:20 a.m.