Triple
T32099067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commentaries on Plato |
E819795
|
entity |
| Predicate | historicalAuthor |
P130537
|
FINISHED |
| Object | Michael Psellos |
—
|
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: Michael Psellos | Statement: [Commentaries on Plato, historicalAuthor, Michael Psellos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalAuthor Context triple: [Commentaries on Plato, historicalAuthor, Michael Psellos]
-
A.
historianAuthor
chosen
Indicates that one entity is the historian who authored or wrote the work represented by the other entity.
-
B.
historicalFigure
Indicates that an entity is recognized as a notable person from the past who played a significant role in history.
-
C.
hasHistoricalWritingInfluenceFrom
Indicates that one entity’s historical writing style, content, or traditions are influenced by those of another entity.
-
D.
historicalPeople
Indicates that the related entities are people who lived in or are associated with a past historical period or context.
-
E.
historian
Indicates that an entity studies, interprets, or writes about past events or historical subjects in relation to another entity.
- 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_69f34901106881908ea893ad504a08be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff7c96e6dc8190b89554480ebcea39 |
completed | May 9, 2026, 6:27 p.m. |
| PD | Predicate disambiguation | batch_69ff7c2381748190ad9a2176e0e478cd |
completed | May 9, 2026, 6:25 p.m. |
Created at: May 1, 2026, 12:26 a.m.