Triple
T23841407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laws of Cricket |
E590996
|
entity |
| Predicate | listsDismissalMethod |
P146535
|
FINISHED |
| Object | bowled |
—
|
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: bowled | Statement: [Laws of Cricket, listsDismissalMethod, bowled]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: listsDismissalMethod Context triple: [Laws of Cricket, listsDismissalMethod, bowled]
-
A.
dismissalModes
chosen
Indicates the ways or conditions under which something (such as a case, request, or entity) can be dismissed, closed, or removed.
-
B.
reasonForDismissal
Indicates the cause or justification for which an entity (such as a person, case, or item) was dismissed, terminated, or removed.
-
C.
couldBeDismissedBy
Indicates that one entity has the authority or power to terminate, remove, or discharge the other from a position, role, or obligation.
-
D.
canDismissCabinet
Indicates that one entity has the authority or power to remove or dismiss a cabinet from its official position.
-
E.
testDismissalsAsKeeper
Indicates the number of times a player, acting as a wicket-keeper, has dismissed opposing players during tests.
- 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.