Triple
T26209588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Arab Emirates national cricket team |
E655446
|
entity |
| Predicate | ODICapacity |
P160046
|
FINISHED |
| Object | 50 overs |
—
|
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: 50 overs | Statement: [United Arab Emirates national cricket team, ODICapacity, 50 overs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ODICapacity Context triple: [United Arab Emirates national cricket team, ODICapacity, 50 overs]
-
A.
operatorCapacity
Indicates the maximum workload or volume of tasks that an operator is able to handle within a given context or time frame.
-
B.
totalCapacity
Indicates the maximum amount or volume that something can hold or accommodate in total.
-
C.
dataCapacity
Indicates the maximum amount of data that something can store, handle, or transmit.
-
D.
unitCapacity
Indicates the maximum quantity or load that a single unit is designed or allowed to hold, process, or accommodate.
-
E.
typicalCapacity
Indicates the usual or standard amount, volume, or capability that something is designed or expected to hold, handle, or perform under normal conditions.
- 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_69ee5b49adb4819086545280d4ef6337 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60d160f60819087ee6aac626327ea |
completed | May 2, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69f5b007ec1c819092e2c3605933f60b |
completed | May 2, 2026, 8:04 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 26, 2026, 8:52 p.m.