Triple
T5581880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICC World Test Championship |
E146658
|
entity |
| Predicate | formatDetails |
P130
|
FINISHED |
| Object | league stage followed by final |
—
|
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: league stage followed by final | Statement: [ICC World Test Championship, formatDetails, league stage followed by final]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formatDetails Context triple: [ICC World Test Championship, formatDetails, league stage followed by final]
-
A.
featuresFormat
Indicates that something (such as a product, service, or medium) is presented, delivered, or made available in a particular format or configuration.
-
B.
format
chosen
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
-
C.
formatSpecialization
Indicates a relationship where one format is a specialized or more specific version of another, more general format.
-
D.
formatMayChange
Indicates that the format or structure of something is subject to modification and may not remain consistent over time.
-
E.
layoutDetail
Indicates the specific arrangement or configuration details of how elements are laid out in relation to each other.
- 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_69c0090287a08190b4098411effe970c |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0208147a48190b2cdb42b9c9814a3 |
completed | March 22, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69c01b147cc081909237f3f2967d4cb8 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:37 p.m.