Triple

T21653582
Position Surface form Disambiguated ID Type / Status
Subject Queen’s Alumni Achievement Award E534399 entity
Predicate customarilyPresentedAt P3021 FINISHED
Object Queen’s alumni events 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: Queen’s alumni events | Statement: [Queen’s Alumni Achievement Award, customarilyPresentedAt, Queen’s alumni events]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: customarilyPresentedAt
Context triple: [Queen’s Alumni Achievement Award, customarilyPresentedAt, Queen’s alumni events]
  • A. presentedTo
    Indicates that something (such as an item, work, or information) was formally given, shown, or introduced by one party to another as the recipient.
  • B. presentedAtTime
    Indicates that an event, action, or item was presented or occurred at a specific point in time.
  • C. displayedAt chosen
    Indicates that one entity is presented or exhibited at a particular location, venue, or event.
  • D. presentedAfter
    Indicates that one entity is presented or displayed at a later time or sequence position than another entity.
  • E. presentedFor
    Indicates that one entity was formally offered, submitted, or shown to another entity for consideration, review, or action.
  • 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_69e0c466aec88190ba39c7543dbc8ba2 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ef59164fe081908abd2e33dcd67def completed April 27, 2026, 12:39 p.m.
PD Predicate disambiguation batch_69e696826c3c81909270791e79760937 completed April 20, 2026, 9:11 p.m.
Created at: April 16, 2026, 6:36 p.m.