Triple
T1336017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asclepius |
E28749
|
entity |
| Predicate | parentageTradition |
P13958
|
FINISHED |
| Object | son of Apollo and Coronis |
—
|
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: son of Apollo and Coronis | Statement: [Asclepius, parentageTradition, son of Apollo and Coronis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentageTradition Context triple: [Asclepius, parentageTradition, son of Apollo and Coronis]
-
A.
parentageVariant
Indicates a relationship where one entity is a variant or alternative form of another entity’s parentage or parental assignment.
-
B.
traditionInheritedFrom
Indicates that a tradition has been passed down or derived from an earlier source, group, or culture.
-
C.
hasChildrenInTradition
Indicates that an entity has one or more children specifically within the context of a particular tradition, lineage, or customary framework.
-
D.
traditionAscribes
chosen
Indicates that a tradition attributes or assigns a particular quality, role, origin, or action to an entity.
-
E.
parentFormation
Indicates that one geological formation serves as the larger or originating unit from which another formation is derived or classified.
- 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_69a498561a508190a3e1bc137c2b866a |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c1ecb5208190a9eadda113c91e66 |
completed | March 1, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69a4bef174708190a07bbc697fe19a2d |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.