Triple
T32932330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Heights |
E842430
|
entity |
| Predicate | usedAsSettingGenre |
P78941
|
FINISHED |
| Object | juvenile detective 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: juvenile detective fiction | Statement: [River Heights, usedAsSettingGenre, juvenile detective fiction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsSettingGenre Context triple: [River Heights, usedAsSettingGenre, juvenile detective fiction]
-
A.
usedGenre
Indicates that one entity employs or is associated with a particular genre in its creation, presentation, or classification.
-
B.
hasGenreAsSetting
chosen
Indicates that a work’s setting is characterized by, or takes place within, a particular genre.
-
C.
hasUseGenre
Indicates that something (such as a work, product, or item) is associated with or categorized under a particular genre for its use or purpose.
-
D.
targetGenre
Indicates the genre that something is specifically aimed at, categorized under, or intended to belong to.
-
E.
usedAsSettingFor
Indicates that one entity serves as the backdrop, location, or environment in which another entity (such as an event, story, or activity) takes place.
- 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_69f34948adfc8190a937f1f622783c0b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fdd5fba5048190b7d430ae2054a1fd |
completed | May 8, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69fdd35f76f88190a1854ea27132f9c7 |
completed | May 8, 2026, 12:13 p.m. |
Created at: May 1, 2026, 1:20 a.m.