Triple
T22604043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Cricket League |
E574907
|
entity |
| Predicate | numberOfDivisionsAtPeak |
P1905
|
FINISHED |
| Object | 8 |
—
|
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: 8 | Statement: [World Cricket League, numberOfDivisionsAtPeak, 8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfDivisionsAtPeak Context triple: [World Cricket League, numberOfDivisionsAtPeak, 8]
-
A.
numberOfPeaks
Indicates the count of distinct peak points or maximum values present within a given entity or dataset.
-
B.
numberOfLocationsAtPeak
Indicates the total count of distinct locations associated with an entity at its highest or peak point in time or activity.
-
C.
numberOfParallelDivisionsAtLevel
Indicates the count of parallel divisions that exist at a specified hierarchical or structural level.
-
D.
numberOfDistrictsPeak
Indicates the maximum number of districts that an entity reaches or has at its highest point over a given period or context.
-
E.
hasNumberOfDivisions
chosen
Indicates the relationship that specifies how many divisions or subunits an entity possesses.
- 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_69e245bc11308190b69d794d5d1e0bb6 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1626fad6881909895cc8c0af62f0d |
completed | April 29, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ee627be4248190889a88764624e174 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 2:51 p.m.