Triple
T8460968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grey College, Bloemfontein |
E200036
|
entity |
| Predicate | notableForSport |
P22
|
FINISHED |
| Object | rugby union |
—
|
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: rugby union | Statement: [Grey College, Bloemfontein, notableForSport, rugby union]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableForSport Context triple: [Grey College, Bloemfontein, notableForSport, rugby union]
-
A.
notableAthlete
Indicates that the subject is a well-known or distinguished athlete associated with the object (such as a sport, team, or organization).
-
B.
notableSportIncluded
Indicates that a particular sport is prominently featured or included as a notable component within something, such as an event, program, or context.
-
C.
knownForSports
Indicates that an entity is recognized or notable for its involvement, achievement, or association with sports.
-
D.
notableFor
chosen
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
E.
notableOutcome
Indicates that an action, event, or entity leads to or is associated with a significant, noteworthy result or consequence.
- 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_69ca83198c4c8190a337bf717d1813f5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4a0ff4c8190b17bbd33db632cea |
completed | March 31, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69cbd0fc634481909842c0a30077bfde |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:10 p.m.