Triple
T24129646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theseus in the Underworld |
E597908
|
entity |
| Predicate | purposeOfDescent |
P154949
|
FINISHED |
| Object | attempt to abduct Persephone |
—
|
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: attempt to abduct Persephone | Statement: [Theseus in the Underworld, purposeOfDescent, attempt to abduct Persephone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purposeOfDescent Context triple: [Theseus in the Underworld, purposeOfDescent, attempt to abduct Persephone]
-
A.
typicalUseOnDescent
Indicates that an object or procedure is commonly used during the descent phase of an activity, operation, or journey.
-
B.
flightPurpose
Indicates the reason or intended purpose for which a particular flight is being taken or operated.
-
C.
plannedLandingMethod
Indicates that an entity has designated a specific method or procedure to be used for its landing.
-
D.
descentVia
Indicates a lineage relationship where one entity is descended from another through one or more intermediate generations or branches.
-
E.
landingMethod
Indicates the manner or technique by which something or someone arrives and comes to rest at a destination, typically from the air or space.
- F. None of above. chosen
Provenance (4 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_69e288c808b881909fed7d18f04bcbbe |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1df7644808190b4bbbf4db1539f48 |
completed | April 29, 2026, 10:37 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
| PDg | Predicate description generation | batch_69f17c28b684819084eea522126463f8 |
completed | April 29, 2026, 3:34 a.m. |
Created at: April 17, 2026, 11:23 p.m.