Triple
T36974437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CSA 4-Day Domestic Series |
E914658
|
entity |
| Predicate | inningsDeclarationAllowed |
P186829
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [CSA 4-Day Domestic Series, inningsDeclarationAllowed, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inningsDeclarationAllowed Context triple: [CSA 4-Day Domestic Series, inningsDeclarationAllowed, yes]
-
A.
mayBeDeclared
Indicates that something has the potential or permission to be formally stated, specified, or announced, but has not necessarily been declared yet.
-
B.
hasBeenDeclaredFor
Indicates that an entity has been officially announced, designated, or proclaimed for a particular purpose, status, or context.
-
C.
declaredTo
Indicates that one entity formally made a statement, announcement, or assertion to another specific entity.
-
D.
declaredInDocument
Indicates that something (such as an entity, concept, or statement) is formally specified or announced within a particular document.
-
E.
containsDeclaration
Indicates that one entity includes or holds within it a formal declaration associated with another entity.
- 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_69f76e8d13b4819089af24a47ce092fc |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fa0a799b9081909bfa8293a22c4b00 |
completed | May 5, 2026, 3:19 p.m. |
Created at: May 3, 2026, 4:14 p.m.