Triple
T23841382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laws of Cricket |
E590996
|
entity |
| Predicate | majorCodeRevision |
P24446
|
FINISHED |
| Object | 1947 |
—
|
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: 1947 | Statement: [Laws of Cricket, majorCodeRevision, 1947]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorCodeRevision Context triple: [Laws of Cricket, majorCodeRevision, 1947]
-
A.
majorRevision
Indicates a substantial change or overhaul made to something, significantly altering its previous form or content.
-
B.
majorRevisionDate
chosen
Indicates the date on which an entity underwent a significant or substantial update or revision.
-
C.
majorVersion
Indicates that one entity specifies or corresponds to the primary (major) version number of another entity in a versioning scheme.
-
D.
majorUpdate
Indicates that a substantial or significant change or revision has been made to something, typically altering its core features or functionality.
-
E.
majorRevisionPeriod
Indicates the time span during which substantial or significant changes are made to something, such as a document, plan, or project.
- 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_69e25d1de32c8190a907afe9c3d6cd6d |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c88797d4819081831fd3f8822ef4 |
completed | April 29, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f1614612b481908c45d99e588882f9 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:08 p.m.