Triple
T18569678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steve Waugh |
E453842
|
entity |
| Predicate | testMatchesAsCaptain |
P132594
|
FINISHED |
| Object | 57 |
—
|
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: 57 | Statement: [Steve Waugh, testMatchesAsCaptain, 57]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testMatchesAsCaptain Context triple: [Steve Waugh, testMatchesAsCaptain, 57]
-
A.
captainedRepresentativeTeam
Indicates that an entity has served as the captain of a representative (e.g., national or regional) team.
-
B.
teamCaptain
Indicates that one entity serves as the captain or designated leader of a particular team.
-
C.
hasNotableCaptain
Indicates that an entity has a specific captain who is recognized as notable or distinguished in some way.
-
D.
isOnlyCaptainToWin
Indicates that the subject is the sole captain ever to have achieved a particular victory or title, with no other captain sharing that distinction.
-
E.
winningCaptain
Indicates that the subject is the captain of a team that has won a particular match, tournament, or competition.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53b01331c8190bec3aba40358a843 |
completed | April 19, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69e478c16e0c8190b03966aa23c395a6 |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484121cd48190bf583b4c94636a30 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:43 a.m.