Triple
T18313523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lonsdale Cup |
E438691
|
entity |
| Predicate | upgradedToGroup3 |
P131291
|
FINISHED |
| Object | 1998 |
—
|
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: 1998 | Statement: [Lonsdale Cup, upgradedToGroup3, 1998]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upgradedToGroup3 Context triple: [Lonsdale Cup, upgradedToGroup3, 1998]
-
A.
upgradedToGroup1
Indicates that an entity has been elevated or transitioned to a higher-status category or group labeled "Group 1".
-
B.
upgradedToGroup1From
Indicates that an entity has been elevated or transitioned into group 1 status from another specified source group or category.
-
C.
wasUpgradedFor
Indicates that one entity was improved, enhanced, or updated specifically to serve, benefit, or be compatible with another entity.
-
D.
upgradedBy
Indicates that an entity has been improved, enhanced, or moved to a higher version or level as a result of actions performed by another entity.
-
E.
promotedToGroup2
Indicates that an entity has been advanced or elevated in status, role, or membership into a second-level group or category.
- 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_69d8b916a2d081909e249e4902f6aad9 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5021b7e2c81908cd3b6684ab899f6 |
completed | April 19, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69e44fe4ee10819086b4142444fca1f5 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a0ba208190a5fe92832a8f7a49 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:36 a.m.