Triple
T37150861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Good Marriage |
E920356
|
entity |
| Predicate | sourceWorkCollection |
P115231
|
FINISHED |
| Object | Full Dark, No Stars |
—
|
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: Full Dark, No Stars | Statement: [A Good Marriage, sourceWorkCollection, Full Dark, No Stars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceWorkCollection Context triple: [A Good Marriage, sourceWorkCollection, Full Dark, No Stars]
-
A.
sourceWorkSection
Indicates that one entity is a specific section or part extracted from a larger source work.
-
B.
sourceWorkWriter
Indicates that a person is the writer or author of the source work associated with another entity.
-
C.
basedOnWorkCollection
chosen
Indicates that something is derived from, adapted from, or otherwise created using a particular collection of works as its source or foundation.
-
D.
hasSourceWork
Indicates that something originates from, is derived from, or is based on a particular source work.
-
E.
sourceWorkStructure
Indicates that one work serves as the structural or organizational basis for another work.
- 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_69f76e9f87c08190b4c8f7fafbd8345a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:15 p.m.