Triple
T31910085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matt Burke |
E814655
|
entity |
| Predicate | stateTeamDebutFor |
P110977
|
FINISHED |
| Object | New South Wales Waratahs |
—
|
NE NERFINISHED |
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: New South Wales Waratahs | Statement: [Matt Burke, stateTeamDebutFor, New South Wales Waratahs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateTeamDebutFor Context triple: [Matt Burke, stateTeamDebutFor, New South Wales Waratahs]
-
A.
notableTeamDebut
Indicates the team for which an entity (typically an athlete) made a debut that is considered particularly significant or noteworthy.
-
B.
debutingTeam
chosen
Indicates that an entity is the team for which another entity (such as a player or work) is making its first official appearance or debut.
-
C.
teamDebutLeague
Indicates the league in which a team made its first official appearance or debut.
-
D.
teamStartYear
Indicates the year in which an entity (such as a person or organization) began its association with a particular team.
-
E.
debutedAsTeam
Indicates that an entity made its first official appearance or start in a particular context as a member of a specified team.
- 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_69f348f109d88190b5005372c53d2fcd |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd82ed2a4c81908bd7797fbd2e3d08 |
completed | May 8, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fd814cc10481908e4f8123d35a5d0c |
completed | May 8, 2026, 6:23 a.m. |
Created at: May 1, 2026, 12:01 a.m.