Triple
T23833941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Method and Politics in Plato’s Statesman |
E589593
|
entity |
| Predicate | aboutWorkBy |
P140090
|
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: [Method and Politics in Plato’s Statesman, aboutWorkBy, Plato]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aboutWorkBy Context triple: [Method and Politics in Plato’s Statesman, aboutWorkBy, Plato]
-
A.
workBy
Indicates that a work (such as a creation, product, or result) is produced, authored, or created by a particular agent or entity.
-
B.
workFor
Indicates that one entity is employed by or performs work under the authority or direction of another entity.
-
C.
appliedWork
Indicates that an entity has put effort, skill, or labor into performing or producing a particular work or task.
-
D.
describesWorkBy
chosen
Indicates that one entity provides a description or account of a work that was created by another entity.
-
E.
workRelatedTo
Indicates a relationship where one entity’s work, tasks, or professional activities are connected, associated, or relevant to those of 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_69e25d1922d481909cab567c06a802ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7f8811c8190b40ae04ec3fa1ee3 |
completed | April 29, 2026, 8:57 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 8:06 p.m.