Triple
T18844119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Rugby Unlocked |
E460869
|
entity |
| Predicate | tieInWith |
P133150
|
FINISHED |
| Object | South African domestic rugby calendar |
—
|
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: South African domestic rugby calendar | Statement: [Super Rugby Unlocked, tieInWith, South African domestic rugby calendar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tieInWith Context triple: [Super Rugby Unlocked, tieInWith, South African domestic rugby calendar]
-
A.
tieForFirstPlace
Indicates that two or more competitors share the highest rank or score, resulting in no single clear winner.
-
B.
maintainsTieWith
Indicates that one entity keeps an ongoing connection or relationship with another entity over time.
-
C.
typeOfTie
Indicates the specific kind or category of relationship or connection that exists between two entities.
-
D.
tieToRankings
Indicates a relationship where something is linked or associated with a specific set of rankings or a ranking system.
-
E.
tieInnings
Indicates that two or more teams or players have finished an innings with the same score, resulting in no winner for that innings.
- F. None of above. chosen
Provenance (4 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5b8ec8c5c8190b15e6394d0018573 |
completed | April 20, 2026, 5:26 a.m. |
| PD | Predicate disambiguation | batch_69e48d1e7dac81909ea1e758c87773c5 |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49785fd7081909577e90a55df0a35 |
completed | April 19, 2026, 8:51 a.m. |
Created at: April 10, 2026, 11:56 a.m.