Triple
T28671682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Periochae |
E725736
|
entity |
| Predicate | authorOfOriginalWorkSummarized |
P166593
|
FINISHED |
| Object | Livy |
—
|
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: Livy | Statement: [Periochae, authorOfOriginalWorkSummarized, Livy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorOfOriginalWorkSummarized Context triple: [Periochae, authorOfOriginalWorkSummarized, Livy]
-
A.
originalWorkBy
Indicates that one entity is the creator or originator of another entity (such as a work, idea, or product).
-
B.
authorOfInspiredWork
Indicates that one entity is the creator or originator of a work that has inspired another work or entity.
-
C.
originAuthor
Indicates that an entity is the original creator or author of another entity (such as a work, document, or idea).
-
D.
authorOrigin
Indicates that an author has a specific place, region, or country as their origin or background.
-
E.
authorOfParentWork
chosen
Indicates that one entity is the author of a work that serves as the parent or source for another related 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_69f01d85be388190b669a0e401e2f2c4 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: April 28, 2026, 5:04 a.m.