Triple
T25809089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Children of Asclepius |
E650054
|
entity |
| Predicate | literarySources |
P10578
|
FINISHED |
| Object | Homeric tradition |
—
|
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: Homeric tradition | Statement: [Children of Asclepius, literarySources, Homeric tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: literarySources Context triple: [Children of Asclepius, literarySources, Homeric tradition]
-
A.
literarySource
chosen
Indicates that one entity serves as the written or literary origin, reference, or basis for another entity.
-
B.
literaryCenter
Indicates that a location functions as a primary hub or focal point for literary activity, such as writing, publishing, or literary culture.
-
C.
literarySubject
Indicates that one entity serves as the subject, topic, or focus of a literary work created by another entity.
-
D.
literaryInterest
Indicates that one entity has an interest in, appreciation of, or engagement with the literary works or writings of another entity.
-
E.
hasLiterarySourceMedium
Indicates that something derives from, is based on, or is expressed through a particular literary medium (such as a book, poem, or script).
- 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_69e7ab35d264819095367f7e80c983ff |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6430a93a48190854ce71df680b2fa |
completed | May 2, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 22, 2026, 7:07 a.m.