Triple
T38402552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frankel |
E900939
|
entity |
| Predicate | debutRacecourse |
P149136
|
FINISHED |
| Object | Newmarket Racecourse |
—
|
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: Newmarket Racecourse | Statement: [Frankel, debutRacecourse, Newmarket Racecourse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: debutRacecourse Context triple: [Frankel, debutRacecourse, Newmarket Racecourse]
-
A.
racingDebut
Indicates the event or moment when an entity first participates in an official race or competitive racing activity.
-
B.
debutVenue
chosen
Indicates the venue or location where an entity (such as a person, group, or work) made its first public appearance or performance.
-
C.
formerRacecourse
Indicates that a location previously functioned as a racecourse but no longer serves that purpose.
-
D.
notableRaceTrackDepicted
Indicates that a work or representation depicts a race track that is considered notable or significant.
-
E.
hasRacecourse
Indicates that an entity possesses, contains, or is associated with a racecourse facility or track.
- 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_69f76e6071a081909eea7a670d21420c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:31 p.m.