Triple
T11708166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lives and Opinions of Eminent Philosophers |
E278299
|
entity |
| Predicate | hasBookDedicatedTo |
P24360
|
FINISHED |
| Object | Epicurus in Book X |
—
|
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: Epicurus in Book X | Statement: [Lives and Opinions of Eminent Philosophers, hasBookDedicatedTo, Epicurus in Book X]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBookDedicatedTo Context triple: [Lives and Opinions of Eminent Philosophers, hasBookDedicatedTo, Epicurus in Book X]
-
A.
dedicatee
chosen
Indicates the person or entity to whom a work, such as a book, artwork, or performance, is formally dedicated.
-
B.
dedicationBy
Indicates that one entity formally dedicates, commits, or devotes another entity (such as a work, resource, or effort) to a particular person, purpose, or cause.
-
C.
dedicateeTitle
Indicates the formal title or honorific held by the person to whom something (such as a work or object) is dedicated.
-
D.
hasBook
Indicates that an entity possesses, owns, or is associated with a particular book.
-
E.
hasDedicationPurpose
Indicates that something is dedicated, devoted, or assigned to serve a particular purpose or function.
- 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_69d6aaff2ce88190b4a1e4b341ad5377 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a49de0388190a063739426bf90e8 |
completed | April 10, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69d88a7d483081909c2a101087515d74 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.