Triple
T25397397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wriddhiman Saha |
E636328
|
entity |
| Predicate | TestDebutRole |
P22824
|
FINISHED |
| Object | wicket-keeper batsman |
—
|
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: wicket-keeper batsman | Statement: [Wriddhiman Saha, TestDebutRole, wicket-keeper batsman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: TestDebutRole Context triple: [Wriddhiman Saha, TestDebutRole, wicket-keeper batsman]
-
A.
testRole
chosen
Indicates that an entity is assigned or associated with a specific role used for testing or validation purposes.
-
B.
testDebut
Indicates the event or context in which an entity (such as a product, feature, or work) is first introduced or used in a testing environment.
-
C.
testDebutFor
Indicates that an entity makes its first appearance or performance in a particular test event, context, or setting.
-
D.
testDebutAgainst
Indicates that an entity’s first test appearance or performance occurs in opposition to, or is evaluated against, a specified counterpart or context.
-
E.
isDebut
Indicates that something is the first formal appearance or introduction of an entity, such as a person, work, or performance, in a particular context or domain.
- 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_69e75db263888190b77fff9e2827b9a2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f584f5dda88190a24d7fb4ab0a45bd |
completed | May 2, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 1:50 p.m.