Triple
T23336805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sylvan, South Carolina |
E591612
|
entity |
| Predicate | genreOfWorkWhereFeatured |
P151918
|
FINISHED |
| Object | coming-of-age 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: coming-of-age fiction | Statement: [Sylvan, South Carolina, genreOfWorkWhereFeatured, coming-of-age fiction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genreOfWorkWhereFeatured Context triple: [Sylvan, South Carolina, genreOfWorkWhereFeatured, coming-of-age fiction]
-
A.
genreOfWorkAbout
Indicates that a work is about a particular genre, expressing that the work’s subject matter or focus concerns that genre.
-
B.
genreOfWorkDescribedIn
Indicates that a work is characterized as belonging to a particular genre as described in another resource or context.
-
C.
genreOfWorkContributedTo
Indicates that an entity contributed to a work belonging to a specified genre.
-
D.
genreOfWorkPerformedIn
Indicates that a specified genre characterizes the type of work that is performed in a particular event, context, or setting.
-
E.
genreOfWorkHonored
Indicates the specific genre or type of creative work for which an honor, award, or recognition is given.
- 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_69e25d20156c81908c5c53195bd9c738 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f197f1e0588190bf073b92be0bf9e4 |
completed | April 29, 2026, 5:32 a.m. |
| PD | Predicate disambiguation | batch_69effcfd8d288190937a887fe6023c11 |
completed | April 28, 2026, 12:19 a.m. |
| PDg | Predicate description generation | batch_69f01d88b4ec8190a2a17a88e0eda178 |
completed | April 28, 2026, 2:38 a.m. |
Created at: April 17, 2026, 5:17 p.m.