Triple
T22844444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prix du Jockey Club |
E566174
|
entity |
| Predicate | modernFormat |
P8393
|
FINISHED |
| Object | run over about 1¼ miles since 2005 |
—
|
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: run over about 1¼ miles since 2005 | Statement: [Prix du Jockey Club, modernFormat, run over about 1¼ miles since 2005]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernFormat Context triple: [Prix du Jockey Club, modernFormat, run over about 1¼ miles since 2005]
-
A.
modernFormSince
chosen
Indicates that an entity has existed in its current or modern form starting from a specified point in time.
-
B.
modernResponse
Indicates that an entity’s reply, solution, or behavior aligns with contemporary standards, practices, or expectations.
-
C.
standardModernForm
Indicates that an entity is expressed or represented in the currently accepted standard modern form of a language, notation, or system.
-
D.
modernUse
Indicates how something is currently used or applied in modern times.
-
E.
historicalFormat
Indicates that something is presented or recorded in a format that was used in the past, reflecting its historical or legacy form.
- 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_69e245869e188190a196584f36e682da |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17e8726d4819095b4d999b4172ff7 |
completed | April 29, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69eed2d117088190acbfe130d84f8627 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:36 p.m.