Triple
T24459309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slade House |
E616772
|
entity |
| Predicate | hasPrologueOrigin |
P156190
|
FINISHED |
| Object | The Right Sort |
—
|
NE NERFINISHED |
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: The Right Sort | Statement: [Slade House, hasPrologueOrigin, The Right Sort]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrologueOrigin Context triple: [Slade House, hasPrologueOrigin, The Right Sort]
-
A.
hasPrologueSometimes
Indicates that an entity occasionally or in some instances includes a prologue.
-
B.
hasPrologueSetting
Indicates that the setting specified is the location or context in which the prologue of a work takes place.
-
C.
hasPrologueCharacter
Indicates that a character appears or is involved in the prologue section of a narrative work.
-
D.
hasPrologueInTitle
Indicates that a work’s title explicitly includes the word “Prologue” or a prologue-related phrase.
-
E.
hasPrologueTheme
Indicates that a work’s prologue centers on, introduces, or is characterized by a particular thematic content or motif.
- 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_69e2d7ef9fe08190a0613908758b4e86 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f298c8d854819091f1d92eef02b1b1 |
completed | April 29, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2:19 a.m.