Triple
T29035878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commentary on Plato's Parmenides |
E737857
|
entity |
| Predicate | mainWorkCommentedOnAuthor |
P142885
|
FINISHED |
| Object | Plato |
—
|
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: Plato | Statement: [Commentary on Plato's Parmenides, mainWorkCommentedOnAuthor, Plato]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainWorkCommentedOnAuthor Context triple: [Commentary on Plato's Parmenides, mainWorkCommentedOnAuthor, Plato]
-
A.
mainWorkCommentedOn
Indicates that a commentary, review, or critical work is focused on and discusses a particular primary work.
-
B.
commentaryWorkFor
Indicates that one entity performs commentary or analysis work on behalf of, or under employment/contract with, another entity.
-
C.
commentedOnBy
Indicates that an entity has received a comment authored or posted by another entity.
-
D.
centralWorkAuthor
chosen
Indicates that an author is the primary creator or main writer responsible for a central or key work.
-
E.
metaComment
Indicates that one statement or comment is about, analyzes, or provides commentary on another statement or comment.
- 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_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6603c9e4081908129011e8294db5a |
completed | May 2, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:58 a.m.