Triple
T5525712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jos Buttler |
E144916
|
entity |
| Predicate | formerTestTeamRole |
P3707
|
FINISHED |
| Object | wicket-keeper-batter for England Test team |
—
|
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-batter for England Test team | Statement: [Jos Buttler, formerTestTeamRole, wicket-keeper-batter for England Test team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerTestTeamRole Context triple: [Jos Buttler, formerTestTeamRole, wicket-keeper-batter for England Test team]
-
A.
testRole
Indicates that an entity is assigned or associated with a specific role used for testing or validation purposes.
-
B.
unitRole
Indicates the functional role or purpose that a unit serves within a larger system or context.
-
C.
roleInTeamViewer
Indicates the specific function, position, or responsibility an entity holds within a TeamViewer-related team or collaborative setup.
-
D.
deFactoRole
chosen
Indicates that an entity effectively functions in a role or capacity in practice, even if that role is not formally or officially assigned.
-
E.
triedRole
Indicates that an entity has attempted to perform, assume, or take on a particular role.
- 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_69c008f873a481909b4d9f7e2db3c37d |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f89112c8190b276317fcc2acce0 |
completed | March 22, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69c01b0a06348190b39ac9fe80d2836a |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:34 p.m.