Triple
T4205585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Long Fatal Love Chase |
E86174
|
entity |
| Predicate | reasonForInitialNonPublication |
P47269
|
FINISHED |
| Object | consideredTooSensational |
—
|
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: consideredTooSensational | Statement: [A Long Fatal Love Chase, reasonForInitialNonPublication, consideredTooSensational]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForInitialNonPublication Context triple: [A Long Fatal Love Chase, reasonForInitialNonPublication, consideredTooSensational]
-
A.
reasonForNonParticipation
Indicates the explanation or cause for why an entity did not take part in a specified activity or event.
-
B.
reasonForSuppression
chosen
Indicates the justification or cause for which something (such as information, data, or content) has been withheld, hidden, or prevented from being shown or used.
-
C.
initialPublication
Indicates the relationship in which a work is first formally published or made publicly available.
-
D.
reasonForPassage
Indicates the underlying cause, motivation, or purpose that explains why a particular passage or movement occurred.
-
E.
mayPublish
Indicates that an entity has the permission or authorization to publish another entity or piece of content.
- 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_69aed93b89f48190a31f6d57c760e42f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03844314819092639ed7d6ef2c6e |
completed | March 9, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69af0196716c81908b99193690630a29 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:49 p.m.