Triple
T14217151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ash Mukherjee |
E352382
|
entity |
| Predicate | fictionalSexualOrientation |
P113259
|
FINISHED |
| Object | gay |
—
|
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: gay | Statement: [Ash Mukherjee, fictionalSexualOrientation, gay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalSexualOrientation Context triple: [Ash Mukherjee, fictionalSexualOrientation, gay]
-
A.
fictionalGender
Indicates that one entity has a gender identity or classification that exists only within a fictional or imaginary context.
-
B.
fictionalLover
Indicates a romantic partner or love interest that exists only within a fictional or imaginary context.
-
C.
fictionalOrigin
Indicates that one entity originates from, or was first introduced within, a fictional work, universe, or narrative created by another entity.
-
D.
fictionalGenre
Indicates that a work of fiction belongs to or is categorized under a particular narrative genre or style.
-
E.
fictionalStatus
Indicates that an entity exists only in imagination or narrative and does not correspond to a real-world counterpart.
- F. None of above. chosen
Provenance (4 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_69d8278a06e481908b5d6af0a8afe737 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6210213481908fac6893e8a9f143 |
completed | April 14, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69de05bcd7d48190a4848d9320404aa6 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239a02e881909b0e2679487e4ab2 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 10, 2026, 1:06 a.m.