Triple
T17960708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Derbyshire County Cricket Club |
E449072
|
entity |
| Predicate | usesNicknameInFormat |
P129903
|
FINISHED |
| Object | Twenty20 cricket |
—
|
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: Twenty20 cricket | Statement: [Derbyshire County Cricket Club, usesNicknameInFormat, Twenty20 cricket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesNicknameInFormat Context triple: [Derbyshire County Cricket Club, usesNicknameInFormat, Twenty20 cricket]
-
A.
usesNicknameOf
Indicates that one entity refers to another entity by a nickname derived from or associated with that other entity’s name.
-
B.
hasNicknameForm
Indicates that one entity is a nickname or informal variant form of another entity’s name.
-
C.
isNickname
Indicates that one name is an informal or alternative name commonly used to refer to the same person or entity as another name.
-
D.
usesNameForm
Indicates that one entity adopts or applies a particular standardized form or variant of a name associated with another entity.
-
E.
usedNicknameSystem
Indicates that one entity referred to another entity using a nickname rather than their formal name.
- 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_69d8b9f8cca8819099836916c56b7c95 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b131fa8481908cd756f350eb6359 |
completed | April 19, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69e3f8f2bd088190b1e22ad4d9cc8b13 |
completed | April 18, 2026, 9:34 p.m. |
| PDg | Predicate description generation | batch_69e42d8d68288190a05dc5d7803cf823 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:22 a.m.