Triple
T4179803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stade Toulousain |
E86565
|
entity |
| Predicate | hasRugbyCode |
P52337
|
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: [Stade Toulousain, hasRugbyCode, rugby union]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRugbyCode Context triple: [Stade Toulousain, hasRugbyCode, rugby union]
-
A.
codeOfRugby
chosen
Indicates that one entity is the specific code or variant of rugby (e.g., rugby union, rugby league) under which the other entity is played, governed, or classified.
-
B.
worldRugbyCode
Indicates that an entity is governed by, follows, or is classified under a specific code or set of rules defined by World Rugby.
-
C.
FIFAcode
Indicates the standardized three-letter country or territory code assigned by FIFA to represent a national football team in international competitions.
-
D.
worldRugbyTrigramme
Indicates that an entity is associated with a specific three-letter code (trigram) used by World Rugby to identify national rugby teams or unions.
-
E.
sportCode
Indicates the specific sport associated with or classified for an entity, typically via a standardized code or identifier.
- 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_69aed93de98c8190ad838ce507b77c8a |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af07078cb081909f64326b12522410 |
completed | March 9, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69af019155448190b19868583272513f |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:45 p.m.