Triple
T17854437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen Elizabeth II Stakes |
E445892
|
entity |
| Predicate | hasGroupStatus |
P129418
|
FINISHED |
| Object | Group 1 |
—
|
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 | Statement: [Queen Elizabeth II Stakes, hasGroupStatus, Group 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGroupStatus Context triple: [Queen Elizabeth II Stakes, hasGroupStatus, Group 1]
-
A.
hasUserGroup
Indicates that a user is associated with, belongs to, or is a member of a specific user group.
-
B.
hasGroupStructure
Indicates that the related entities together form an algebraic group under a specified operation, satisfying closure, associativity, identity, and invertibility.
-
C.
hasCategoryGroup
Indicates that something is associated with, or belongs to, a broader grouping of related categories.
-
D.
hasClientGroup
Indicates that an entity is associated with, or belongs to, a particular group of clients.
-
E.
belongsToGroup
Indicates that an entity is a member of, or is included within, a particular group or collection.
- 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_69d8b9f26f18819089c9e43250bee6ae |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e49001d8b881908c8d4efc3d7ff04f |
completed | April 19, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e266888190ae976b4b7d5b886f |
completed | April 18, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69e3f022ec448190a9bf191be1c5f570 |
completed | April 18, 2026, 8:57 p.m. |
Created at: April 10, 2026, 10:17 a.m.