Triple
T3299930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wally Lewis |
E69303
|
entity |
| Predicate | StateOfOriginSeriesWinsAsCaptain |
P47843
|
FINISHED |
| Object | 8 |
—
|
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: 8 | Statement: [Wally Lewis, StateOfOriginSeriesWinsAsCaptain, 8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: StateOfOriginSeriesWinsAsCaptain Context triple: [Wally Lewis, StateOfOriginSeriesWinsAsCaptain, 8]
-
A.
winningCaptain
Indicates that the subject is the captain of a team that has won a particular match, tournament, or competition.
-
B.
captainODI
Indicates that the subject serves as the captain of the object’s team in One Day International (ODI) cricket matches.
-
C.
homeTeamCaptain
Indicates that one entity serves as the captain of the home team in a given game or match in relation to the other entity.
-
D.
hasNotableCaptain
Indicates that an entity has a specific captain who is recognized as notable or distinguished in some way.
-
E.
captainPosition
Indicates that an entity holds the role or position of captain in relation to another entity (such as a team, vessel, or group).
- F. None of above. chosen
Provenance (4 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_69ad859e529c8190a404273f53cb487d |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0a66fcc819093931fe7a6507723 |
completed | March 8, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_69ada42407dc81909f60d7a14e1b7934 |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada526764881908e4bd52938d5374d |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:11 p.m.