Triple
T30373091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coronation Stakes |
E772602
|
entity |
| Predicate | hasGroupStatusSince |
P19818
|
FINISHED |
| Object | Group 1 (from 1988) |
—
|
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: Group 1 (from 1988) | Statement: [Coronation Stakes, hasGroupStatusSince, Group 1 (from 1988)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGroupStatusSince Context triple: [Coronation Stakes, hasGroupStatusSince, Group 1 (from 1988)]
-
A.
hasGroupStatus
Indicates that an entity possesses a particular status, role, or condition within a group or collective context.
-
B.
hasHistorySince
Indicates that an entity has maintained a particular state, condition, or relationship continuously starting from a specified point in time.
-
C.
hasSubgroupStatus
Indicates that one group holds a specific status or classification as a subgroup within a larger group or organization.
-
D.
groupStatusIntroduced
Indicates that a group has been newly created or formally introduced into a system or context.
-
E.
currentStatusSince
chosen
Indicates the point in time since which an entity has held its current status or state.
- 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_69f2248d71408190aec0d5c2001b1cff |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 29, 2026, 7:59 p.m.