Triple

T29245755
Position Surface form Disambiguated ID Type / Status
Subject Portorosso Cup triathlon E741436 entity
Predicate targetParticipantsInStory P190487 FINISHED
Object children of Portorosso 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: children of Portorosso | Statement: [Portorosso Cup triathlon, targetParticipantsInStory, children of Portorosso]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: targetParticipantsInStory
Context triple: [Portorosso Cup triathlon, targetParticipantsInStory, children of Portorosso]
  • A. targetConsumerInStory
    Indicates that a specified consumer is the intended or focal target within the context of a particular story or narrative.
  • B. partnerInStory
    Indicates that two or more entities are partners or collaborators within the context of a specific story or narrative.
  • C. audienceWithinStory
    Indicates that an audience exists as an internal, in-story observer or listener within the narrative itself, rather than outside it.
  • D. ownerInStory
    Indicates that one entity is the owner of another entity within the context or narrative of a specific story.
  • E. associatedWithPersonInStory
    Indicates that one entity has a connection or involvement with a specific person within the context of a story.
  • 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_69f0911eba2c8190b07cd2fdf91422c9 completed April 28, 2026, 10:51 a.m.
NER Named-entity recognition batch_69fcc7779d248190afdb348a95375443 completed May 7, 2026, 5:10 p.m.
PD Predicate disambiguation batch_69fcc58566a0819082d5ea36e03bf0c6 completed May 7, 2026, 5:01 p.m.
PDg Predicate description generation batch_69fcc73264e08190b0b5917f32226fae completed May 7, 2026, 5:09 p.m.
Created at: April 28, 2026, 12:32 p.m.