Triple
T32339883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amaze Entertainment |
E826280
|
entity |
| Predicate | developedGameType |
P174059
|
FINISHED |
| Object | action game |
—
|
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: action game | Statement: [Amaze Entertainment, developedGameType, action game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedGameType Context triple: [Amaze Entertainment, developedGameType, action game]
-
A.
gameGenreDeveloped
chosen
Indicates that a particular game genre has been created, defined, or developed by a specific entity (such as a person, team, or organization).
-
B.
developedGameBasedOn
Indicates that one game was created or designed using another game as its source of inspiration, foundation, or reference.
-
C.
includesGameType
Indicates that one entity contains or supports a particular type or category of game.
-
D.
developedSystemFor
Indicates that one entity created or engineered a system intended to be used by or on behalf of another entity.
-
E.
notableGameType
Indicates that a game is of a particular type or category for which the subject is especially well known or notable.
- 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_69f34913d9048190befaa634025232be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 1, 2026, 12:48 a.m.