Triple
T31661095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buller Rugby Football Union |
E808002
|
entity |
| Predicate | hasRepresentativeTeamType |
P146139
|
FINISHED |
| Object | senior men |
—
|
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: senior men | Statement: [Buller Rugby Football Union, hasRepresentativeTeamType, senior men]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRepresentativeTeamType Context triple: [Buller Rugby Football Union, hasRepresentativeTeamType, senior men]
-
A.
representedByTeam
Indicates that an entity is officially or formally represented by a specific team.
-
B.
teamTypePlayedFor
chosen
Indicates the type or category of team (e.g., national, club, youth) that an entity has played for.
-
C.
representsTeamsIn
Indicates that one entity serves as a representative or agent on behalf of a team or multiple teams.
-
D.
hasNotableTeamType
Indicates that an entity is associated with a team that is recognized as having a specific notable type or category.
-
E.
representsSportTeamsOf
Indicates that one entity is a sports team that represents, is affiliated with, or acts on behalf of another entity (such as a city, institution, or organization).
- 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_69f348daf95c81908b4c985b7ddcd0b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a018f9c7cf88190adc5daf3806f2077 |
completed | May 11, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_6a018ca4e0e481908091f0c1f8a4c31b |
completed | May 11, 2026, 8 a.m. |
Created at: April 30, 2026, 10:57 p.m.