Triple
T33835066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colin Slade |
E867208
|
entity |
| Predicate | playsOrPlayedInCompetition |
P10753
|
FINISHED |
| Object | Super Rugby |
—
|
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: Super Rugby | Statement: [Colin Slade, playsOrPlayedInCompetition, Super Rugby]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsOrPlayedInCompetition Context triple: [Colin Slade, playsOrPlayedInCompetition, Super Rugby]
-
A.
competitionPlayed
Indicates that a competitive event or match has taken place between participants.
-
B.
playedInTournament
chosen
Indicates that an entity participated as a competitor or player in a specific tournament.
-
C.
hasCompetition
Indicates that one entity is in a state of rivalry or contest with another entity, typically competing for the same goal, resource, or advantage.
-
D.
playsInNationalCompetitions
Indicates that an entity participates as a competitor in national-level competitions or tournaments.
-
E.
competedAs
Indicates that an entity participated in a competition or contest in the role, category, or capacity specified by another entity.
- 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: May 1, 2026, 1:47 a.m.