Triple
T7943574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knebworth Park 1996 |
E184445
|
entity |
| Predicate | attendancePerNight |
P2636
|
FINISHED |
| Object | approximately 125000 |
—
|
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: approximately 125000 | Statement: [Knebworth Park 1996, attendancePerNight, approximately 125000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attendancePerNight Context triple: [Knebworth Park 1996, attendancePerNight, approximately 125000]
-
A.
attendance
chosen
Indicates the relationship between an event and the people who are present at or participate in that event.
-
B.
fanAttendance
Indicates the number or presence of fans attending an event, such as a game, show, or performance.
-
C.
visitorFrequency
Indicates how often a visitor comes to or interacts with a particular entity or location.
-
D.
peakDayAttendance
Indicates the number of attendees present on the single highest-attendance day within a given period or event.
-
E.
laterAttends
Indicates that one entity attends an event or place at a time later than another referenced attendance.
- 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_69ca8291c2008190b1b8832c87814bcf |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b0d31548190af54a2f3bbb8cad3 |
completed | March 31, 2026, 3:10 a.m. |
| PD | Predicate disambiguation | batch_69cae93526d081909303265bf60419fd |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:09 p.m.