Triple
T35706021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peaceful Warrior |
E1031718
|
entity |
| Predicate | hasBookSource |
P45645
|
FINISHED |
| Object | Way of the Peaceful Warrior: A Book That Changes Lives |
—
|
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: Way of the Peaceful Warrior: A Book That Changes Lives | Statement: [Peaceful Warrior, hasBookSource, Way of the Peaceful Warrior: A Book That Changes Lives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBookSource Context triple: [Peaceful Warrior, hasBookSource, Way of the Peaceful Warrior: A Book That Changes Lives]
-
A.
hasBook
Indicates that an entity possesses, owns, or is associated with a particular book.
-
B.
hasBookSetIn
Indicates that a book’s story takes place in, or is primarily set within, a particular location.
-
C.
containsBook
Indicates that one entity (typically a container or collection) includes a specific book as part of its contents.
-
D.
hasBookForm
Indicates that something exists or is available in the form of a book.
-
E.
hasSourceWork
chosen
Indicates that something originates from, is derived from, or is based on a particular source work.
- 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_69f76e0d393c8190b6303c64408736db |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fdf5d05cc481909ec9e1b1f0784279 |
completed | May 8, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69fdf0cdd6948190838864ab3120dfa6 |
completed | May 8, 2026, 2:18 p.m. |
Created at: May 3, 2026, 4:05 p.m.