Triple
T34537718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regina Rugby Club |
E886714
|
entity |
| Predicate | playedCodeOfFootball |
P115258
|
FINISHED |
| Object | rugby football |
—
|
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 football | Statement: [Regina Rugby Club, playedCodeOfFootball, rugby football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playedCodeOfFootball Context triple: [Regina Rugby Club, playedCodeOfFootball, rugby football]
-
A.
playsFootballCode
chosen
Indicates that an entity participates in or is involved with a specific code or variant of football (e.g., soccer, rugby, American football).
-
B.
playedAssociationFootball
Indicates that an entity has participated in playing the sport of association football (soccer).
-
C.
playsAssociationFootballUnderRulesOf
Indicates that one entity participates in association football following the rules or regulations established by another entity.
-
D.
playedCode
Indicates that an entity performed or executed a specific piece of code.
-
E.
playsAssociationFootballIn
Indicates that an entity participates in playing association football (soccer) within or for a specified place, organization, or context.
- 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 1, 2026, 2:02 a.m.