Triple
T29102912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commentary on Plato's Alcibiades I |
E736685
|
entity |
| Predicate | authorInOriginalLanguage |
P23529
|
FINISHED |
| Object | Proclus |
—
|
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: Proclus | Statement: [Commentary on Plato's Alcibiades I, authorInOriginalLanguage, Proclus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorInOriginalLanguage Context triple: [Commentary on Plato's Alcibiades I, authorInOriginalLanguage, Proclus]
-
A.
originalLanguageAuthor
Indicates that an author created a work in a particular original language.
-
B.
authorOrigin
Indicates that an author has a specific place, region, or country as their origin or background.
-
C.
originAuthor
chosen
Indicates that an entity is the original creator or author of another entity (such as a work, document, or idea).
-
D.
authorOfTranslation
Indicates that one entity is the person or agent who produced a translated version of a work originally created in another language.
-
E.
authorTraditionallyAscribedTo
Indicates that authorship of a work is customarily or historically attributed to an entity, even if definitive proof of authorship may be uncertain or disputed.
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: April 28, 2026, 11:13 a.m.