Triple
T28899073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nemesis |
E732903
|
entity |
| Predicate | belongsToGenreFamily |
P124610
|
FINISHED |
| Object | classic arcade shooters |
—
|
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: classic arcade shooters | Statement: [Nemesis, belongsToGenreFamily, classic arcade shooters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToGenreFamily Context triple: [Nemesis, belongsToGenreFamily, classic arcade shooters]
-
A.
hasGenreRelation
chosen
Indicates that there is an association between an entity and a specific genre, specifying the type or category it belongs to.
-
B.
genreAssociatedViaFamily
Indicates that a genre is connected to another entity through a familial or family-based relationship rather than a direct or primary association.
-
C.
hasGenreInRoles
Indicates that an entity participates in roles associated with a particular genre or set of genres.
-
D.
associatedWithGenreElement
Indicates that something has a connection or linkage to a specific genre-related element (such as a motif, convention, or stylistic feature).
-
E.
includedInGenreCollection
Indicates that something is a member of, or contained within, a specific genre-based collection.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fd3d46d1f48190a1b20dd063224b7d |
completed | May 8, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69fd3ae1510c81908fe1280efc17feee |
completed | May 8, 2026, 1:22 a.m. |
Created at: April 28, 2026, 8:01 a.m.