Triple
T24903356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newmarket Handicap |
E623637
|
entity |
| Predicate | homeStraight |
P157469
|
FINISHED |
| Object | Flemington straight-six |
—
|
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: Flemington straight-six | Statement: [Newmarket Handicap, homeStraight, Flemington straight-six]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeStraight Context triple: [Newmarket Handicap, homeStraight, Flemington straight-six]
-
A.
homeTo
Indicates that a place serves as the primary location, residence, or habitat for a person, group, or thing.
-
B.
homeFront
Indicates a relationship where an entity is associated with the domestic sphere or civilian side of a conflict, typically supporting war efforts away from the battlefield.
-
C.
homeStand
Indicates that an entity plays or appears at its own home venue or location, typically as the host side in a series of events or games.
-
D.
homeFeature
Indicates that a home possesses or includes a particular feature or amenity.
-
E.
house1
Indicates that something is identified or classified as a house or dwelling.
- 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_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f4303fad6c8190844f069164f0904d |
completed | May 1, 2026, 4:46 a.m. |
Created at: April 18, 2026, 5:27 a.m.