Triple

T896824
Position Surface form Disambiguated ID Type / Status
Subject contest of the bow in Ithaca E19363 entity
Predicate purposeInStory P79 FINISHED
Object selection of a husband for Penelope 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: selection of a husband for Penelope | Statement: [contest of the bow in Ithaca, purposeInStory, selection of a husband for Penelope]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: purposeInStory
Context triple: [contest of the bow in Ithaca, purposeInStory, selection of a husband for Penelope]
  • A. purpose chosen
    Indicates that one entity exists, is done, or is used in order to achieve, support, or serve the goal, function, or intended outcome of another entity.
  • B. depictionPurpose
    Indicates that one entity is depicted specifically for the purpose or function it serves in relation to another entity.
  • C. role
    Indicates the function, position, or responsibility that one entity holds in relation to another within a given context.
  • D. mainProtagonist
    Indicates that the subject is the central character or primary focus in the narrative of the related work.
  • E. roleInDialogue
    Indicates that an entity participates in a dialogue with a specific conversational role (e.g., speaker, listener, moderator) relative to other participants.
  • 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_69a4939d37188190848be3d426ebc9ae completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4ad2550c88190a624eb5627d472ad completed March 1, 2026, 9:18 p.m.
PD Predicate disambiguation batch_69a4aa94f7c881908deeb62308942e19 completed March 1, 2026, 9:07 p.m.
Created at: March 1, 2026, 7:39 p.m.