Triple
T36965275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Double Helix Games |
E914411
|
entity |
| Predicate | developedGameForPlatform |
P39167
|
FINISHED |
| Object | Xbox 360 |
—
|
NE NERFINISHED |
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: Xbox 360 | Statement: [Double Helix Games, developedGameForPlatform, Xbox 360]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedGameForPlatform Context triple: [Double Helix Games, developedGameForPlatform, Xbox 360]
-
A.
platformsDevelopedFor
chosen
Indicates the platforms (e.g., operating systems, devices, or environments) for which something has been specifically created or adapted.
-
B.
developsOnPlatform
Indicates that one entity is created, built, or developed using the tools, services, or environment provided by another platform entity.
-
C.
gameGenreDeveloped
Indicates that a particular game genre has been created, defined, or developed by a specific entity (such as a person, team, or organization).
-
D.
developedSystemFor
Indicates that one entity created or engineered a system intended to be used by or on behalf of another entity.
-
E.
developedGameBasedOn
Indicates that one game was created or designed using another game as its source of inspiration, foundation, or reference.
- 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fdd92396788190ae1424bc1ae55844 |
completed | May 8, 2026, 12:37 p.m. |
| PD | Predicate disambiguation | batch_69fdd678f40481909a717a2daec83b36 |
completed | May 8, 2026, 12:26 p.m. |
Created at: May 3, 2026, 4:14 p.m.