Triple
T37663849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Singularity (EP) |
E937775
|
entity |
| Predicate | isInGenreContextOf |
P136689
|
FINISHED |
| Object | non-game Lena Raine works |
—
|
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: non-game Lena Raine works | Statement: [Singularity (EP), isInGenreContextOf, non-game Lena Raine works]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInGenreContextOf Context triple: [Singularity (EP), isInGenreContextOf, non-game Lena Raine works]
-
A.
isInGenreContext
chosen
Indicates that something occurs, is interpreted, or is relevant within the scope or framework of a particular genre.
-
B.
hasNotableGenreContext
Indicates that an entity’s genre is significant or noteworthy in understanding its context, interpretation, or impact.
-
C.
hasGenreScope
Indicates that something (such as a work, collection, or classification) is limited to, defined by, or applicable within a particular genre or set of genres.
-
D.
containsGenreElement
Indicates that something includes or incorporates an element characteristic of a particular genre.
-
E.
hasGenreInRoles
Indicates that an entity participates in roles associated with a particular genre or set of genres.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.