Triple
T18111027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yorkshire Cup |
E433472
|
entity |
| Predicate | elevatedToGroup2 |
P129772
|
FINISHED |
| Object | 1971 |
—
|
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: 1971 | Statement: [Yorkshire Cup, elevatedToGroup2, 1971]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevatedToGroup2 Context triple: [Yorkshire Cup, elevatedToGroup2, 1971]
-
A.
promotedToGroup2
chosen
Indicates that an entity has been advanced or elevated in status, role, or membership into a second-level group or category.
-
B.
elevatedTo
Indicates that one entity is promoted or raised to a higher rank, status, position, or level relative to another.
-
C.
upgradedToGroup1
Indicates that an entity has been elevated or transitioned to a higher-status category or group labeled "Group 1".
-
D.
SecondStepElevation
Indicates that an entity occupies or reaches a second, higher level or step relative to a lower reference level.
-
E.
secondaryUserGroup
Indicates a relationship where a user is associated with an additional, non-primary group that supplements their main group membership.
- 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddd2038081909515fb6d17495cbf |
completed | April 19, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_69e43313ca788190baa224269e71de49 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:28 a.m.