Triple
T36988334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cupid |
E915024
|
entity |
| Predicate | notableTrackOfWin |
P205679
|
FINISHED |
| Object | Oaklawn Park |
E860675
|
NE 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: Oaklawn Park | Statement: [Cupid, notableTrackOfWin, Oaklawn Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableTrackOfWin Context triple: [Cupid, notableTrackOfWin, Oaklawn Park]
-
A.
notableWin
Indicates that one entity achieved a particularly significant or distinguished victory over another or in a specific event.
-
B.
notableWinType
Indicates that the relationship specifies the particular category or type of a notable victory associated with an entity.
-
C.
notableWinner
Indicates that the subject is a particularly distinguished or prominent winner of the referenced competition, award, or contest.
-
D.
notableTrack
Indicates that a particular track (such as a song or recording) is especially significant, well-known, or prominent in relation to the subject.
-
E.
notableOutcome
Indicates that an action, event, or entity leads to or is associated with a significant, noteworthy result or consequence.
- F. None of above. chosen
Provenance (5 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_69f76e8dd0408190b8b46da118ea5128 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3e2c52dae4819081c1f0291a849d7d |
completed | June 26, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:14 p.m.