Triple
T30128960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Immortal Coils |
E765775
|
entity |
| Predicate | publicationTypeOfContainingWork |
P218
|
FINISHED |
| Object | science book |
—
|
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: science book | Statement: [Immortal Coils, publicationTypeOfContainingWork, science book]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicationTypeOfContainingWork Context triple: [Immortal Coils, publicationTypeOfContainingWork, science book]
-
A.
publicationTypeOf
Indicates that one entity specifies the type or category of publication to which another publication entity belongs.
-
B.
publicationType
chosen
Indicates the specific category or format of a published work that characterizes how it is issued or presented.
-
C.
publicationOfWork
Indicates that a particular work has been formally made public, typically through printing, distribution, or release by a publisher or similar entity.
-
D.
publicationOpus
Indicates that a work or opus has been published, linking the creative work to its publication event or status.
-
E.
publicationTitle
Indicates the name or title under which a work (such as an article, book, or paper) is formally published.
- 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_69fdb04ed81c8190b8feea90c1c785a6 |
completed | May 8, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69fda9d6c5148190a63205b6d9b0a1b4 |
completed | May 8, 2026, 9:16 a.m. |
Created at: April 29, 2026, 7:14 p.m.