Triple
T24469355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FTC World Championship |
E617056
|
entity |
| Predicate | gameChanges |
P19084
|
FINISHED |
| Object | every season |
—
|
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: every season | Statement: [FTC World Championship, gameChanges, every season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameChanges Context triple: [FTC World Championship, gameChanges, every season]
-
A.
gameplayImpact
Indicates how one element in a game affects the mechanics, difficulty, or overall experience of playing that game.
-
B.
tacticalChange
Indicates a deliberate adjustment in strategy, methods, or actions made to improve effectiveness in a specific situation or operation.
-
C.
notableRuleChange
chosen
Indicates a significant modification to an established rule or set of rules that meaningfully alters how they apply or are enforced.
-
D.
notableChange
Indicates a significant alteration or shift in the state, condition, or characteristics of an entity or relationship.
-
E.
gameEngineModification
Indicates a relationship where an entity alters, extends, or customizes the functionality or behavior of a game engine.
- 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.