Triple
T10910404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twenty20 International cricket |
E257681
|
entity |
| Predicate | powerplayOvers |
P96364
|
FINISHED |
| Object | 1–6 |
—
|
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: 1–6 | Statement: [Twenty20 International cricket, powerplayOvers, 1–6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerplayOvers Context triple: [Twenty20 International cricket, powerplayOvers, 1–6]
-
A.
powerBy
Indicates that one entity operates, functions, or is made possible through the energy, resources, or enabling capabilities provided by another entity.
-
B.
powerLevel
Indicates the degree or intensity of power or strength possessed by an entity in a given context.
-
C.
emphasizesPowerOver
Indicates a relationship where one entity highlights, prioritizes, or asserts dominance, control, or authority over another.
-
D.
powerUp
Indicates an action where an entity increases or restores another entity’s energy, strength, or functional capacity.
-
E.
powerPosition
Indicates that one entity holds a position of authority, control, or dominance over another within a hierarchy or power structure.
- 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_69d6aa864ed88190818280ab6791d065 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d77071492c8190bd6f8623a59464c9 |
completed | April 9, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69d70d3f9dc88190a686a8b0dd6a3b21 |
completed | April 9, 2026, 2:21 a.m. |
| PDg | Predicate description generation | batch_69d710400ea88190ac2ed6f0a13d62c1 |
completed | April 9, 2026, 2:34 a.m. |
Created at: April 8, 2026, 9:22 p.m.