Triple
T16369626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hothouse Flower |
E397529
|
entity |
| Predicate | hasProseStyle |
P35511
|
FINISHED |
| Object | commercial fiction |
—
|
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: commercial fiction | Statement: [Hothouse Flower, hasProseStyle, commercial fiction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProseStyle Context triple: [Hothouse Flower, hasProseStyle, commercial fiction]
-
A.
hasProseElements
Indicates that something contains or is composed of prose components, such as sentences, paragraphs, or narrative text.
-
B.
hasProseAndVerse
Indicates that something contains both prose and verse forms within it.
-
C.
hasProseDialogue
Indicates that one entity contains or features spoken or conversational content expressed in prose form involving another entity.
-
D.
hasVerseStyle
Indicates that one entity is characterized by, or presented in, the verse style specified by another entity.
-
E.
rhetoricalStyle
chosen
Indicates the characteristic manner or technique of expression used in communication, such as tone, structure, and persuasive strategies.
- 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_69d87f2778dc8190aa95c7572db127e6 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2ff4021e88190ad093bab74cf82a4 |
completed | April 18, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69e226f37ecc819082af58b29b4e39d1 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:08 a.m.