Triple
T38064065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sha Tin Racecourse |
E950422
|
entity |
| Predicate | hasNotableMeeting |
—
|
GENERATED |
| Object | Hong Kong International Races |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableMeeting Context triple: [Sha Tin Racecourse, hasNotableMeeting, Hong Kong International Races]
-
A.
hasMeeting
Indicates that one entity is scheduled to participate in or hold a meeting with another entity or at a specific time or place.
-
B.
hasMeetings
Indicates that an entity participates in or is associated with one or more scheduled meetings.
-
C.
hasMeetingSchedule
Indicates that an entity has an associated plan or timetable specifying when meetings are to occur.
-
D.
notableMeeting
chosen
Indicates that two or more entities participated together in a meeting considered significant or noteworthy in some context.
-
E.
hasPrimaryMeeting
Indicates that an entity is associated with its main or most important meeting, distinguishing it from other meetings it may have.
- F. None of above.
Provenance (1 batch)
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_69f76f01e63c819093b6012fc974f35a |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:21 p.m.