Triple
T14508037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Miseducation of Cameron Post |
E340316
|
entity |
| Predicate | placeInStory |
P9801
|
FINISHED |
| Object | conversion therapy center |
—
|
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: conversion therapy center | Statement: [The Miseducation of Cameron Post, placeInStory, conversion therapy center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeInStory Context triple: [The Miseducation of Cameron Post, placeInStory, conversion therapy center]
-
A.
positionInStory
Indicates the point or role an event, character, or element occupies within the overall sequence or structure of a story.
-
B.
placeInSeries
Indicates the position or order that something occupies within a sequence or series.
-
C.
storyElement
Indicates that one entity functions as a narrative component or part within the structure of another entity’s story.
-
D.
locationOfNarrative
chosen
Indicates the place or setting where the events or story described in the narrative occur.
-
E.
setInFictionalLocation
Indicates that an event, story, or narrative takes place within a fictional or imagined location rather than a real-world setting.
- 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_69d822d9c0408190b9a2b3643e58bb4d |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69de94e40e44819084f323f8f9982b75 |
completed | April 14, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69de5c4ccba08190a988bfda0bc9f5cb |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:21 a.m.