Triple
T36479614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ireland Wolfhounds |
E898772
|
entity |
| Predicate | usesRugbyCode |
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: [Ireland Wolfhounds, usesRugbyCode, rugby union]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRugbyCode Context triple: [Ireland Wolfhounds, usesRugbyCode, 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.
hasRugbyReputation
Indicates that an entity is recognized or regarded for its involvement, performance, or standing in rugby.
-
D.
roleInRugby
Indicates the specific position or function an entity holds within the context of playing or participating in rugby.
-
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_69f76e5a0e088190a2b6706aeb41723c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:10 p.m.