Triple
T28114008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Gauteng rugby region |
E710568
|
entity |
| Predicate | countryRugbyUnion |
P56671
|
FINISHED |
| Object | South African Rugby Union |
—
|
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: South African Rugby Union | Statement: [Northern Gauteng rugby region, countryRugbyUnion, South African Rugby Union]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryRugbyUnion Context triple: [Northern Gauteng rugby region, countryRugbyUnion, South African Rugby Union]
-
A.
countryRepresentedInInternationalRugby
Indicates that an entity has represented a specific country in international rugby competition.
-
B.
homeCountryRugbyUnion
chosen
Indicates the country that serves as the primary national rugby union affiliation or base for an entity.
-
C.
homeCountryRugbyCode
Indicates the type or code of rugby that is primarily associated with an entity’s home country.
-
D.
worldRugbyRegion
Indicates the regional governing body or geographic region under World Rugby with which an entity is affiliated or associated.
-
E.
playedRugbyUnionFor
Indicates that one entity was a member of and competed for a particular rugby union team 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_69ef9b72f63081909dfbc2c1ddae86c6 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69fdee770af48190aca2670db50f8b49 |
completed | May 8, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69fdecec98a08190a357d816dc2a6dbe |
completed | May 8, 2026, 2:02 p.m. |
Created at: April 27, 2026, 9:13 p.m.