Triple
T3523388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bet365 Gold Cup |
E74478
|
entity |
| Predicate | meeting |
P49217
|
FINISHED |
| Object | Sandown end-of-season meeting |
—
|
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: Sandown end-of-season meeting | Statement: [Bet365 Gold Cup, meeting, Sandown end-of-season meeting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meeting Context triple: [Bet365 Gold Cup, meeting, Sandown end-of-season meeting]
-
A.
meetingType
Indicates the specific category or format of a meeting that characterizes how it is organized or conducted.
-
B.
meetingContext
Indicates the situational setting, circumstances, or background conditions in which a meeting takes place.
-
C.
conference
Indicates that an entity organizes, hosts, or is associated with a formal meeting or event where participants gather to discuss specific topics or share information.
-
D.
meetingDay
Indicates the specific day on which a meeting is scheduled or takes place between the related entities.
-
E.
meetingNumber
Indicates the specific numerical identifier assigned to distinguish one meeting from others.
- 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_69ad85d0c5488190a3d8e02ebd01a1aa |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc4f16b8819094ad2755670ddc7b |
completed | March 8, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69adae121a048190b03825a001d21f49 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb21a437c81908bca88d5e123d744 |
completed | March 8, 2026, 5:30 p.m. |
Created at: March 8, 2026, 3:19 p.m.