Triple
T37097053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aiden Markram |
E918590
|
entity |
| Predicate | hasPlayedCricketFormat |
P114962
|
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: [Aiden Markram, hasPlayedCricketFormat, Test cricket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlayedCricketFormat Context triple: [Aiden Markram, hasPlayedCricketFormat, Test cricket]
-
A.
hasPlayedDomesticCricketFor
Indicates that a person has been a member of and played domestic-level cricket matches for a specified team or organization.
-
B.
playedInCricketWorldCup
Indicates that an entity has participated as a player in at least one Cricket World Cup tournament.
-
C.
hasPlayedInT20League
Indicates that an entity (typically a player) has participated in at least one Twenty20 (T20) cricket league.
-
D.
hasPlayedFormat
chosen
Indicates that an entity (such as a player or performer) has participated in or engaged with a particular format or type of activity.
-
E.
typeOfCricket
Indicates that one entity is a specific kind or category of cricket in relation to another entity.
- 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_69f76e9a48bc8190a3947508d8bca408 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe349879848190bcd77e3cc3470458 |
completed | May 8, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69fe31e3cf908190b23ebc2f7fe58722 |
completed | May 8, 2026, 6:56 p.m. |
Created at: May 3, 2026, 4:14 p.m.