Triple
T26209487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cricket |
E655443
|
entity |
| Predicate | hasTestMatchDuration |
P53726
|
FINISHED |
| Object | up to five days |
—
|
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: up to five days | Statement: [Cricket, hasTestMatchDuration, up to five days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTestMatchDuration Context triple: [Cricket, hasTestMatchDuration, up to five days]
-
A.
supportsTestDuration
Indicates that one entity is capable of handling, accommodating, or being compatible with a specified duration for a test or testing process.
-
B.
typicalTestDuration
chosen
Indicates the usual or expected length of time required to complete a given test.
-
C.
testMatches
Indicates that a given test case or pattern corresponds to, satisfies, or correctly aligns with a specified input, condition, or expected outcome.
-
D.
testMatchStatus
Indicates the current state or outcome of a specific test match within its lifecycle (e.g., scheduled, in progress, completed, or cancelled).
-
E.
hasMatch
Indicates that one entity corresponds to, aligns with, or is considered an equivalent or suitable counterpart to another entity.
- 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_69ee5b49adb4819086545280d4ef6337 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 26, 2026, 8:52 p.m.