Triple
T23359346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael Bevan |
E593140
|
entity |
| Predicate | formatPlayedForAustralia |
P18320
|
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: [Michael Bevan, formatPlayedForAustralia, Test cricket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formatPlayedForAustralia Context triple: [Michael Bevan, formatPlayedForAustralia, Test cricket]
-
A.
representativeAppearancesForAustralia
Indicates that the subject has representative appearances made on behalf of Australia, typically in an official or competitive context.
-
B.
playedFor
Indicates that one entity has been a member of or participated as a player for a particular team, organization, or group.
-
C.
AFLPremiershipsAsPlayerWith
Indicates that a person has won one or more AFL premierships while playing for a specified team.
-
D.
hasPlayedForNationalTeam
chosen
Indicates that an athlete has been a member of and appeared in competition for a specified national team.
-
E.
laterPlayedFor
Indicates that an individual was a member of or played for a team or organization at a time after a previously referenced team or organization.
- 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_69e25d24d2a4819092e6ede74c2a918d |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f19a1a39988190b4b4993b80d5a5f6 |
completed | April 29, 2026, 5:41 a.m. |
| PD | Predicate disambiguation | batch_69effcfd8d288190937a887fe6023c11 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:29 p.m.