Triple
T24903488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flemington Racecourse railway station |
E623640
|
entity |
| Predicate | notableEventServed |
P175938
|
FINISHED |
| Object | Melbourne Cup Carnival |
—
|
NE NERFINISHED |
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: Melbourne Cup Carnival | Statement: [Flemington Racecourse railway station, notableEventServed, Melbourne Cup Carnival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEventServed Context triple: [Flemington Racecourse railway station, notableEventServed, Melbourne Cup Carnival]
-
A.
notableEventMentionedIn
Indicates that a particular notable event is referenced or discussed within a specified source or document.
-
B.
notableEventResponse
Indicates a response, reaction, or consequence that occurs as a result of a notable event.
-
C.
notableEventIncluded
Indicates that a particular notable event is contained within, or forms part of, a larger collection, record, or context.
-
D.
notableEventPromoted
Indicates that an event was actively publicized, advertised, or otherwise promoted as notable or significant.
-
E.
notableSubevent
Indicates that one event is a particularly significant or noteworthy component within a larger, encompassing event.
- 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_69e2fac797cc8190b30d77f4121099ac |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f6db3606808190a80c6e9f5da5b33e |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6db1bc348819097c844f76e2fa4fe |
completed | May 3, 2026, 5:20 a.m. |
Created at: April 18, 2026, 5:27 a.m.