Triple
T16338888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Test cricket |
E396743
|
entity |
| Predicate | declarationRule |
P123029
|
FINISHED |
| Object | captain may declare innings closed |
—
|
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: captain may declare innings closed | Statement: [Test cricket, declarationRule, captain may declare innings closed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: declarationRule Context triple: [Test cricket, declarationRule, captain may declare innings closed]
-
A.
compositionRule
Indicates how multiple elements or components are combined or arranged according to a specific rule or pattern.
-
B.
displayRule
Indicates the rule or condition that determines how something should be visually presented or displayed.
-
C.
deFactoRuleStart
Indicates the point in time or condition at which a rule begins to apply in practice, regardless of its formal or official start.
-
D.
styleOfRule
Indicates the stylistic or formatting convention that a particular rule follows or is expressed in.
-
E.
declared
Indicates that an entity formally announces, states, or proclaims something, often with official or authoritative intent.
- 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2da08fbc88190a31127d10ca633d6 |
completed | April 18, 2026, 1:10 a.m. |
| PD | Predicate disambiguation | batch_69e226eba9b48190af6e80d3d1c2aed3 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24555bb6c8190977cf5c5f9149056 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:07 a.m.