Triple
T1364155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Conduct of Life |
E29163
|
entity |
| Predicate | workInAuthorCorpus |
P19302
|
FINISHED |
| Object | late-career work of Ralph Waldo Emerson |
—
|
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: late-career work of Ralph Waldo Emerson | Statement: [The Conduct of Life, workInAuthorCorpus, late-career work of Ralph Waldo Emerson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workInAuthorCorpus Context triple: [The Conduct of Life, workInAuthorCorpus, late-career work of Ralph Waldo Emerson]
-
A.
yearWorkWritten
Indicates the year in which a particular work was written or created.
-
B.
positionInAuthorOeuvre
chosen
Indicates the relative placement or order of a work within an author's overall body of work.
-
C.
partOfAuthorBibliography
Indicates that a work is included in the set of publications that make up an author's bibliography.
-
D.
authorshipEvidence
Indicates evidence or justification supporting a claim that one entity is the author or creator of another.
-
E.
workBy
Indicates that a work (such as a creation, product, or result) is produced, authored, or created by a particular agent or entity.
- 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_69a498d77abc8190913bf57e5f51d2c4 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c2b5d05c81908b49e282648e073a |
completed | March 1, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69a4bef945c08190a027472fdd695ea5 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:57 p.m.