Triple
T30128958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Immortal Coils |
E765775
|
entity |
| Predicate | workInWhichAppears |
P93872
|
FINISHED |
| Object | The Selfish Gene |
—
|
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 Selfish Gene | Statement: [Immortal Coils, workInWhichAppears, The Selfish Gene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workInWhichAppears Context triple: [Immortal Coils, workInWhichAppears, The Selfish Gene]
-
A.
appearsInWorkByAuthorFrom
Indicates that an entity appears in a work that was created by an author originating from a specified place or country.
-
B.
appearsInWorkByTitle
chosen
Indicates that an entity appears in, is featured in, or is contained within a work identified by its title.
-
C.
appearsInWorkAbout
Indicates that an entity is mentioned or featured within a work whose subject or focus is that entity.
-
D.
workInThisPublication
Indicates that an entity performs work or contributes within the context of the specified publication.
-
E.
settingOfWorkAppearsIn
Indicates that a particular place, time, or environment serves as the setting within which a given creative work’s events or narrative occur.
- 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_69f22477d1a081908df2b7e6ed16859d |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67e4658088190962d0b05f9149b0b |
completed | May 2, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:14 p.m.