Triple
T11882331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alcibiades I |
E282688
|
entity |
| Predicate | traditionallyIncludedIn |
P11158
|
FINISHED |
| Object | Platonic corpus |
—
|
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: Platonic corpus | Statement: [Alcibiades I, traditionallyIncludedIn, Platonic corpus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionallyIncludedIn Context triple: [Alcibiades I, traditionallyIncludedIn, Platonic corpus]
-
A.
traditionallyIncludes
Indicates that something customarily or historically contains or incorporates something else as a standard or expected part.
-
B.
traditionIncludes
Indicates that a particular tradition encompasses, contains, or is composed of a specified element, practice, or component.
-
C.
traditionallyOneOf
chosen
Indicates that something is customarily or historically considered to belong to a specific set, category, or group.
-
D.
traditionallyFoundIn
Indicates that something is customarily or historically located, used, or present within a particular place, context, or setting.
-
E.
formerlyIncluded
Indicates that an entity was previously part of, contained in, or a member of another entity, but is no longer included.
- 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_69d6ab2a90b08190a4e818821cc93e6d |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8d39d2934819093b9f7006f45e5cb |
completed | April 10, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69d8bb272f88819090c37c944c5a60ab |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:44 p.m.