Triple
T22283853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shreyas Iyer |
E550806
|
entity |
| Predicate | hasFormatExperience |
P141157
|
FINISHED |
| Object | Test cricket |
—
|
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: Test cricket | Statement: [Shreyas Iyer, hasFormatExperience, Test cricket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormatExperience Context triple: [Shreyas Iyer, hasFormatExperience, Test cricket]
-
A.
hasPastExperience
Indicates that an entity has previously engaged in or undergone the specified activity, role, or situation in the past.
-
B.
hasExperienceOf
chosen
Indicates that one entity has undergone, encountered, or lived through a particular event, situation, or activity associated with another entity.
-
C.
hasExperienceElement
Indicates that an experience is composed of, or includes, a specific constituent element or component.
-
D.
typeOfExperience
Indicates that one entity specifies the category or nature of an experience associated with another entity.
-
E.
hasNotableExperience
Indicates that an entity has a significant or distinguished experience related to another entity or context.
- 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_69e11e44d538819097c6b8f333af3352 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15605a8448190906a0ab9ffa4260b |
completed | April 29, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69e72ff0363081909f794d19c8a64837 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:40 p.m.