Triple
T19450744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Breakout |
E486606
|
entity |
| Predicate | successiveLevels |
P98366
|
FINISHED |
| Object | increasing difficulty as bricks are cleared |
—
|
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: increasing difficulty as bricks are cleared | Statement: [Breakout, successiveLevels, increasing difficulty as bricks are cleared]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successiveLevels Context triple: [Breakout, successiveLevels, increasing difficulty as bricks are cleared]
-
A.
upperLevels
Indicates that one entity occupies or corresponds to higher levels, tiers, or hierarchical positions relative to another entity.
-
B.
followsLevel
chosen
Indicates that one entity comes after or succeeds another in a defined sequence, stage, or hierarchical level.
-
C.
successiveIndividuals
Indicates that one individual directly follows another in a sequence or ordered progression.
-
D.
successorGroups
Indicates that one group is the direct successor or follow-up group to another group in some sequence or lineage.
-
E.
successorLeagueLevel
Indicates that one league level directly follows another in a hierarchical sequence, representing the next higher or lower tier in the league 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6338db7c081908793f23592ebef6b |
completed | April 20, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd6e806081909053f325ba01ab6b |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:38 p.m.