Triple
T31946183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R1 button |
E815656
|
entity |
| Predicate | commonUseGenre |
P83033
|
FINISHED |
| Object | first-person shooter |
—
|
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: first-person shooter | Statement: [R1 button, commonUseGenre, first-person shooter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonUseGenre Context triple: [R1 button, commonUseGenre, first-person shooter]
-
A.
commonGenre
Indicates that two entities share at least one genre in common.
-
B.
commonGenreContext
Indicates that two or more entities share a similar or related genre context, such as belonging to the same or closely related genres.
-
C.
usedGenre
chosen
Indicates that one entity employs or is associated with a particular genre in its creation, presentation, or classification.
-
D.
genreWithin
Indicates that one genre is a subgenre or more specific category contained within another, broader genre.
-
E.
targetGenre
Indicates the genre that something is specifically aimed at, categorized under, or intended to belong to.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe0d165a48819098b854318a50d76c |
completed | May 8, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69fe0931002481908a95b34f95e9f64e |
completed | May 8, 2026, 4:02 p.m. |
Created at: May 1, 2026, 12:06 a.m.