Triple
T17960693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Derbyshire County Cricket Club |
E449072
|
entity |
| Predicate | firstClassStatusGranted |
P129902
|
FINISHED |
| Object | 1871 |
—
|
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: 1871 | Statement: [Derbyshire County Cricket Club, firstClassStatusGranted, 1871]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstClassStatusGranted Context triple: [Derbyshire County Cricket Club, firstClassStatusGranted, 1871]
-
A.
firstPartyStatus
Indicates that an entity holds the role or position of the primary or original party in a given relationship, agreement, or interaction.
-
B.
fareClassAccess
Indicates that a particular fare class grants access or eligibility to a specified service, benefit, or booking option.
-
C.
hasNobleStatus
Indicates that an entity possesses a recognized noble rank, title, or aristocratic status.
-
D.
eliteStatusProgram
Indicates a relationship where an entity is enrolled in or associated with a special high-tier or privileged status program.
-
E.
VIPStatus
Indicates that an entity holds a special or privileged status compared to others, often granting enhanced access, benefits, or priority treatment.
- 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.