Triple
T36974594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lungi Ngidi |
E914662
|
entity |
| Predicate | internationalCricketFormat |
P146528
|
FINISHED |
| Object | Test |
—
|
NE NERFINISHED |
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: Test | Statement: [Lungi Ngidi, internationalCricketFormat, Test]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: internationalCricketFormat Context triple: [Lungi Ngidi, internationalCricketFormat, Test]
-
A.
worldCupFormat
Indicates the specific structure, rules, and progression system used to organize and play a given World Cup competition.
-
B.
typeOfCricket
chosen
Indicates that one entity is a specific kind or category of cricket in relation to another entity.
-
C.
usesLimitedOversRules
Indicates that the action or event is conducted under limited-overs rules, typically involving a fixed maximum number of overs per side.
-
D.
wonICCWorldT20
Indicates that the subject has emerged as the champion of the ICC World Twenty20 (T20) cricket tournament.
-
E.
isInternationalCricketer
Indicates that a person plays or has played cricket at the international level, representing a country in officially recognized matches.
- 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_69f76e8d13b4819089af24a47ce092fc |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fec00f27988190955de6b6348a4d97 |
completed | May 9, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69febd52037c8190b475dbd50fdbc13e |
completed | May 9, 2026, 4:51 a.m. |
Created at: May 3, 2026, 4:14 p.m.