Triple
T23841429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laws of Cricket |
E590996
|
entity |
| Predicate | includesLaw |
P116428
|
FINISHED |
| Object | Law 1: The players |
—
|
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: Law 1: The players | Statement: [Laws of Cricket, includesLaw, Law 1: The players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesLaw Context triple: [Laws of Cricket, includesLaw, Law 1: The players]
-
A.
containsLaw
chosen
Indicates that one entity (such as a document, code, or jurisdiction) includes or encompasses a specific law within it.
-
B.
containsLawOn
Indicates that one entity (such as a document, code, or regulation) includes or sets forth legal provisions concerning another entity or subject.
-
C.
containsLawType
Indicates that one entity includes or is associated with a specific type or category of law.
-
D.
usesLawTo
Indicates that one entity applies or relies on a specific law as a means or tool to affect, regulate, or influence another entity or situation.
-
E.
legalMatters
Indicates that one entity is involved with, concerned about, or responsible for legal issues, processes, or obligations related to another entity or context.
- 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.