Triple
T34507757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Love and Ruin |
E885932
|
entity |
| Predicate | writtenBySameAuthorAs |
P98868
|
FINISHED |
| Object | The Paris Wife |
—
|
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 Paris Wife | Statement: [Love and Ruin, writtenBySameAuthorAs, The Paris Wife]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writtenBySameAuthorAs Context triple: [Love and Ruin, writtenBySameAuthorAs, The Paris Wife]
-
A.
workBySameAuthorAs
chosen
Indicates that two works share the same author, i.e., they were created by the same person or entity.
-
B.
hasAuthorOfSameWorkAs
Indicates that two authors are related by having written or contributed to the same work.
-
C.
complementsWorkBySameAuthor
Indicates that one work enhances, completes, or supplements another work created by the same author.
-
D.
authorOfSameGenre
Indicates that two authors primarily write works within the same literary genre.
-
E.
coAuthorAlsoWrote
Indicates that a person who is a co-author of one work also wrote another work, linking shared authorship across multiple creations.
- 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_69f349cc0220819081f154c6964f4dc2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f727bde8f88190ad746ca515134ca1 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72739c30c81908642eef3feb3afcf |
completed | May 3, 2026, 10:45 a.m. |
Created at: May 1, 2026, 2:01 a.m.