Triple
T36508365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scotland national rugby sevens team |
E899829
|
entity |
| Predicate | worldRugbyCountryCode |
P38354
|
FINISHED |
| Object | SCO |
—
|
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: SCO | Statement: [Scotland national rugby sevens team, worldRugbyCountryCode, SCO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worldRugbyCountryCode Context triple: [Scotland national rugby sevens team, worldRugbyCountryCode, SCO]
-
A.
countryRepresentedInInternationalRugby
Indicates that an entity has represented a specific country in international rugby competition.
-
B.
worldRugbyTrigramme
chosen
Indicates that an entity is associated with a specific three-letter code (trigram) used by World Rugby to identify national rugby teams or unions.
-
C.
worldRugbyCode
Indicates that an entity is governed by, follows, or is classified under a specific code or set of rules defined by World Rugby.
-
D.
homeCountryRugbyCode
Indicates the type or code of rugby that is primarily associated with an entity’s home country.
-
E.
homeCountryRugbyUnion
Indicates the country that serves as the primary national rugby union affiliation or base for an entity.
- 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_69f76e5dada881909da2d34bc7a9202a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fec8aef1d8819094c7fd7074038e6b |
completed | May 9, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69fec639876481908efd84a3631a4271 |
completed | May 9, 2026, 5:29 a.m. |
Created at: May 3, 2026, 4:10 p.m.