Triple
T8800228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lessons in Life and Business |
E209386
|
entity |
| Predicate | subtitleOfWorkType |
P9208
|
FINISHED |
| Object | motivational 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: motivational book | Statement: [Lessons in Life and Business, subtitleOfWorkType, motivational book]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subtitleOfWorkType Context triple: [Lessons in Life and Business, subtitleOfWorkType, motivational book]
-
A.
subtitle
Indicates that one work serves as a secondary or explanatory title to another, typically appearing beneath the main title.
-
B.
partOfWorkType
Indicates that something is a component, subtype, or specific category within a broader type of work.
-
C.
subjectOfWork
Indicates that one entity is the main topic, focus, or theme that a particular work (such as a book, article, or artwork) is about.
-
D.
subtitleDFunction
chosen
Indicates a functional relationship where one entity serves as the subtitle or secondary textual label for another entity.
-
E.
subjectType
Indicates the classification or category that defines what kind of entity the subject is.
- 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_69ca836320e48190b5cf585b90a322c4 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5fb8aab88190befed16301e08efc |
completed | March 31, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1f28ec8190a34311cb412920c2 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:44 p.m.