Triple
T7324627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aethra |
E168837
|
entity |
| Predicate | inMyth |
P62913
|
FINISHED |
| Object | birth of Theseus |
—
|
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: birth of Theseus | Statement: [Aethra, inMyth, birth of Theseus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inMyth Context triple: [Aethra, inMyth, birth of Theseus]
-
A.
usesMythOf
Indicates that one entity employs or invokes a myth or mythical narrative about another entity as part of its actions, explanations, or representations.
-
B.
mythVariant
chosen
Indicates that one mythological narrative is a version, retelling, or alternative form of another myth.
-
C.
originMyth
Indicates the traditional myth or legendary narrative that explains the beginnings or creation of a people, place, institution, or phenomenon.
-
D.
settingOfMyth
Indicates that a location or environment serves as the backdrop or context in which a particular myth takes place.
-
E.
subsequentMythology
Indicates that one mythology develops later than, or is derived from, another mythology in time or tradition.
- 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_69c68a54cacc81908e3b773441f19566 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f04993408190b73fb46d83a632d5 |
completed | March 27, 2026, 9:02 p.m. |
| PD | Predicate disambiguation | batch_69c6e77230048190b2c29ca6b3a65b8e |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:03 p.m.