Triple
T15116723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Australia cricket team |
E361057
|
entity |
| Predicate | limitedOversStatus |
P57803
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [South Australia cricket team, limitedOversStatus, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: limitedOversStatus Context triple: [South Australia cricket team, limitedOversStatus, true]
-
A.
usesLimitedOversRules
chosen
Indicates that the action or event is conducted under limited-overs rules, typically involving a fixed maximum number of overs per side.
-
B.
isLimitOf
Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
-
C.
lawsOfTheGameStatus
Indicates the status or condition of the applicable rules or laws governing how a game is played.
-
D.
limitedIssueOf
Indicates that one entity is issued or made available in a restricted or finite quantity by another entity.
-
E.
typicalInningsOversLimit
Indicates the standard maximum number of overs allotted to an innings in a given cricket format or competition.
- 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_69d85a0491ec8190830960be8fafb994 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0059ca9048190b742e70e818ee64f |
completed | April 15, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69deb96c1d9c81909351558ed97bc5b7 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:05 a.m.