Triple
T14214674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orlando |
E352315
|
entity |
| Predicate | centralToGenreDiscussion |
P113243
|
FINISHED |
| Object | queer literature |
—
|
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: queer literature | Statement: [Orlando, centralToGenreDiscussion, queer literature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralToGenreDiscussion Context triple: [Orlando, centralToGenreDiscussion, queer literature]
-
A.
genreWithin
Indicates that one genre is a subgenre or more specific category contained within another, broader genre.
-
B.
mainGenreShiftTo
Indicates a change in the primary genre classification of something from one main genre to another.
-
C.
commonGenre
Indicates that two entities share at least one genre in common.
-
D.
becameCentralGenreIn
Indicates that one genre developed into or was recognized as the primary or dominant genre within a particular context, period, or domain.
-
E.
targetGenre
Indicates the genre that something is specifically aimed at, categorized under, or intended to belong to.
- 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_69de620f07bc81909212dcd1c91b5f95 |
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.