Triple
T30249299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flappy Bird |
E769150
|
entity |
| Predicate | gameOverCondition |
P159759
|
FINISHED |
| Object | collision with pipes |
—
|
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: collision with pipes | Statement: [Flappy Bird, gameOverCondition, collision with pipes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameOverCondition Context triple: [Flappy Bird, gameOverCondition, collision with pipes]
-
A.
hasGameEndCondition
chosen
Indicates that an entity specifies the condition or set of conditions under which a game is considered finished or concluded.
-
B.
hasWinningCondition
Indicates that a particular condition or set of conditions determines when a participant, entity, or process is considered to have won or successfully completed a defined objective.
-
C.
conditionOfVictory
Indicates the specific circumstances or criteria under which a participant is considered to have won.
-
D.
gameOfDeath
Indicates a relationship where an entity is involved in, associated with, or characterized by a lethal contest, challenge, or deadly event.
-
E.
gameOutcome
Indicates the result or final status of a game, such as which side won, lost, or if it ended in a draw.
- 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_69f224831dc08190b2e569b987264057 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68079a50c819090a11d215f3dd4b0 |
completed | May 2, 2026, 10:53 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:40 p.m.