Triple

T4034105
Position Surface form Disambiguated ID Type / Status
Subject Griffin Park E83785 entity
Predicate recordAttendanceContext P14459 FINISHED
Object FA Cup match vs Leicester City in 1949 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: FA Cup match vs Leicester City in 1949 | Statement: [Griffin Park, recordAttendanceContext, FA Cup match vs Leicester City in 1949]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: recordAttendanceContext
Context triple: [Griffin Park, recordAttendanceContext, FA Cup match vs Leicester City in 1949]
  • A. recordAttendance
    Indicates that an entity documents or logs the presence or participation of another entity at a specific event, session, or time.
  • B. recordAttendanceCompetition chosen
    Indicates that an entity records or logs attendance information for a competition or competitive event.
  • C. attendance
    Indicates the relationship between an event and the people who are present at or participate in that event.
  • D. recordSettingVenueFor
    Indicates the venue or location where a particular record (such as a performance, achievement, or measurement) was set.
  • E. recordHeld
    Indicates that one entity possesses or maintains a particular record associated with another entity or context.
  • 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_69aed92e29ac819080f7a98b594fec05 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aefb11d92481909aaebbc250ff45b9 completed March 9, 2026, 4:53 p.m.
PD Predicate disambiguation batch_69aef8fe440c819093a7fa22c4ff3f1a completed March 9, 2026, 4:44 p.m.
Created at: March 9, 2026, 3:36 p.m.