Triple
T36974446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CSA 4-Day Domestic Series |
E914658
|
entity |
| Predicate | pointSystemFeature |
P135252
|
FINISHED |
| Object | bonus points for batting |
—
|
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: bonus points for batting | Statement: [CSA 4-Day Domestic Series, pointSystemFeature, bonus points for batting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pointSystemFeature Context triple: [CSA 4-Day Domestic Series, pointSystemFeature, bonus points for batting]
-
A.
pointType
Indicates the specific category or classification assigned to a point within a given context or system.
-
B.
pointsSystemManagedBy
Indicates that the points system is overseen, controlled, or administered by a specified managing entity.
-
C.
pointsType
Indicates that one entity is classified as a specific type or category of points associated with another entity.
-
D.
pointDefinition
Indicates that one entity serves as the defining description or specification of a particular point in another entity.
-
E.
featuresScoringSystem
chosen
Indicates that one entity incorporates or provides a particular scoring or rating system as part of its functionality or design.
- 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_69f76e8d13b4819089af24a47ce092fc |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:14 p.m.