Triple
T5279025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yorkshire County Cricket Club |
E119443
|
entity |
| Predicate | recordStatus |
P63826
|
FINISHED |
| Object | most County Championship titles |
—
|
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: most County Championship titles | Statement: [Yorkshire County Cricket Club, recordStatus, most County Championship titles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordStatus Context triple: [Yorkshire County Cricket Club, recordStatus, most County Championship titles]
-
A.
statusRecordedBy
Indicates that the status of an entity was documented or captured by a specific agent or system.
-
B.
historicalRecordStatus
Indicates the status or condition of a record within a historical or archival context (e.g., active, archived, revised, or obsolete).
-
C.
recordHeld
Indicates that one entity possesses or maintains a particular record associated with another entity or context.
-
D.
recordHeldIn
Indicates that a record is stored, maintained, or kept within a particular location, system, or repository.
-
E.
recordsType
Indicates that one entity documents, stores, or keeps an official account of a particular type or category of information, event, or item.
- 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_69bd446d05a8819092ad333a3f9c8d5c |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd8c9c72b08190947b6b955ac1bb5a |
completed | March 20, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69bd844a56b48190ad743c42246e02dd |
completed | March 20, 2026, 5:30 p.m. |
| PDg | Predicate description generation | batch_69bd8c9b82ac819080e798713c0bb4d8 |
completed | March 20, 2026, 6:06 p.m. |
Created at: March 20, 2026, 1:52 p.m.