Triple
T33534693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waterworld (SNES, cancelled) |
E858885
|
entity |
| Predicate | plannedGenre |
P82410
|
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: [Waterworld (SNES, cancelled), plannedGenre, action game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedGenre Context triple: [Waterworld (SNES, cancelled), plannedGenre, action game]
-
A.
targetGenre
chosen
Indicates the genre that something is specifically aimed at, categorized under, or intended to belong to.
-
B.
possibleGenre
Indicates that something may belong to, be classified under, or be associated with a particular genre as one of several potential genre options.
-
C.
visualGenre
Indicates the visual or stylistic category to which something belongs, such as its artistic or cinematic genre.
-
D.
promotedGenre
Indicates that a particular genre is being actively highlighted, advertised, or given preferential visibility or status.
-
E.
favoriteGenre
Indicates that one entity’s preferred or most liked genre, among several possible genres, is the other entity.
- 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_69f34978caf4819083f90eba4944d8e8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 1, 2026, 1:39 a.m.