Triple
T8473555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amelius Gentilianus |
E200335
|
entity |
| Predicate | roleInPlotinianSchool |
P30024
|
FINISHED |
| Object | prominent disciple |
—
|
LITERAL FINISHED |
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: prominent disciple | Statement: [Amelius Gentilianus, roleInPlotinianSchool, prominent disciple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInPlotinianSchool Context triple: [Amelius Gentilianus, roleInPlotinianSchool, prominent disciple]
-
A.
hasPhilosophicalRole
chosen
Indicates that an entity occupies, performs, or is associated with a specific role or function within a philosophical context or discourse.
-
B.
workInPlatoCorpus
Indicates that an entity is a work that appears within the corpus of texts attributed to Plato.
-
C.
workOfPhilosopher
Indicates that the subject is a philosophical work created or authored by the philosopher represented by the object.
-
D.
roleInTheology
Indicates the specific function, position, or significance an entity holds within a theological system, doctrine, or belief framework.
-
E.
roleInTheory
Indicates the specific function, position, or contribution that an entity has within a particular theory or theoretical framework.
- 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_69ca831a4f348190bfdd09250e86ae35 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4f7328481909ad19bcf8d182022 |
completed | March 31, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69cbd104250c8190b4c499dcc9937494 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:11 p.m.