Triple

T5469919
Position Surface form Disambiguated ID Type / Status
Subject Erymanthian Boar E122804 entity
Predicate fateAfterCapture P3146 FINISHED
Object brought alive to Eurystheus 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: brought alive to Eurystheus | Statement: [Erymanthian Boar, fateAfterCapture, brought alive to Eurystheus]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: fateAfterCapture
Context triple: [Erymanthian Boar, fateAfterCapture, brought alive to Eurystheus]
  • A. capturedOff
    Indicates that one entity has taken another entity away or into custody, removing it from its original location or control.
  • B. wasRecapturedBy
    Indicates that an entity which had previously escaped or been released was caught again by another entity.
  • C. capturedFor
    Indicates that one entity has been taken into custody, control, or possession specifically for the benefit, use, or purpose of another entity.
  • D. capturedDuring
    Indicates that one event or state occurred within the temporal span of another, typically representing that something was recorded, seized, or documented while a specific situation or activity was taking place.
  • E. fate chosen
    Indicates that an entity is destined or predetermined to experience a particular outcome or course of events beyond its control.
  • 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_69bd46459ff48190823377457bcf7128 completed March 20, 2026, 1:06 p.m.
NER Named-entity recognition batch_69bd927c946c8190aef40679199fede3 completed March 20, 2026, 6:31 p.m.
PD Predicate disambiguation batch_69bd91a370a88190b5d17b8a5387138d completed March 20, 2026, 6:27 p.m.
Created at: March 20, 2026, 2:09 p.m.