Triple
T31439264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pushmo series |
E802021
|
entity |
| Predicate | levelEditor |
P171874
|
FINISHED |
| Object | supports QR code sharing of levels |
—
|
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: supports QR code sharing of levels | Statement: [Pushmo series, levelEditor, supports QR code sharing of levels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: levelEditor Context triple: [Pushmo series, levelEditor, supports QR code sharing of levels]
-
A.
mapDesigner
Indicates that an entity is the designer or creator responsible for producing a particular map.
-
B.
hasLevelDesign
Indicates that one entity possesses, is associated with, or is defined by a particular level design created or specified by another entity.
-
C.
artEditor
Indicates that one entity serves as the art editor (responsible for overseeing and refining artistic or visual content) for another entity or work.
-
D.
trackDesigner
Indicates that one entity is the designer or creator responsible for the layout or structure of a track associated with another entity.
-
E.
laterEditor
Indicates that one entity served as an editor of a work at a later time or in a subsequent edition relative to another editor.
- F. None of above. chosen
Provenance (4 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_69f348c5a6bc819092a557e95438976f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a5f656ec81909e02b0b873303adf |
completed | May 3, 2026, 1:33 a.m. |
Created at: April 30, 2026, 9:04 p.m.