Triple
T13093098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Challenge Cup |
E310511
|
entity |
| Predicate | finalAttendanceType |
P65012
|
FINISHED |
| Object | large crowd event |
—
|
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: large crowd event | Statement: [Challenge Cup, finalAttendanceType, large crowd event]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalAttendanceType Context triple: [Challenge Cup, finalAttendanceType, large crowd event]
-
A.
hasAttendanceType
chosen
Indicates the specific category or mode of attendance associated with an event or participant (e.g., in-person, virtual, hybrid).
-
B.
attendance
Indicates the relationship between an event and the people who are present at or participate in that event.
-
C.
hasTypicalAttendance
Indicates the usual or characteristic number of attendees associated with an event, venue, or activity.
-
D.
attendanceAnnounced
Indicates that an official statement has been made about whether and/or how many people will attend an event.
-
E.
attendancePromotion
Indicates a relationship where one entity promotes, encourages, or incentivizes attendance at an event, activity, or location for another entity.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d9813cd1b881909871a318fdd60672 |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d9803f6c508190bfadfbc2d00c2c64 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:03 p.m.