Triple
T8136710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fountain of Tears |
E189989
|
entity |
| Predicate | genreOfInspiredWork |
P40291
|
FINISHED |
| Object | narrative poem |
—
|
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: narrative poem | Statement: [Fountain of Tears, genreOfInspiredWork, narrative poem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genreOfInspiredWork Context triple: [Fountain of Tears, genreOfInspiredWork, narrative poem]
-
A.
genreOfOriginWork
Indicates that a work is classified under a particular genre based on the genre of its original source work.
-
B.
genreOfInspiration
chosen
Indicates that one entity serves as the inspirational genre or stylistic source for the creation, style, or classification of another entity.
-
C.
literaryGenreOfWork
Indicates that a work belongs to or is classified under a particular literary genre.
-
D.
adaptedWorkOf
Indicates that one work is derived from, based on, or reinterprets the content of another pre-existing work.
-
E.
notableWorkGenre
Indicates that a particular work is recognized as notable for an entity and specifies the genre to which that work belongs.
- 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_69ca82bd9900819099477cdc2eb4244f |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb440171d48190afa4a312ab19389c |
completed | March 31, 2026, 3:48 a.m. |
| PD | Predicate disambiguation | batch_69cb369c0d0481908762c488d7f77e74 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:35 p.m.