Triple
T17989259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lethbridge Bulls |
E430323
|
entity |
| Predicate | hasLeagueScope |
P126599
|
FINISHED |
| Object | regional |
—
|
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: regional | Statement: [Lethbridge Bulls, hasLeagueScope, regional]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLeagueScope Context triple: [Lethbridge Bulls, hasLeagueScope, regional]
-
A.
hasOppositeLeagueScope
Indicates that two entities are associated with leagues whose scopes are opposite in nature (e.g., one local vs. one global, or one minor vs. one major).
-
B.
hasScope
Indicates that one entity defines, limits, or encompasses the range, extent, or applicability within which another entity operates or is valid.
-
C.
hasCompetitionScope
Indicates the extent or boundaries within which a competition, contest, or competitive activity is defined or applies.
-
D.
includesLeague
Indicates that an entity (such as a competition, organization, or system) contains or encompasses a specific league as one of its components.
-
E.
notableLeagueScope
chosen
Indicates that the relationship or action pertains to the scope or level (e.g., local, national, international) of a league in which an entity is notably involved or recognized.
- 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_69d8b90364248190a37381adea932f42 |
completed | April 10, 2026, 8:46 a.m. |
| NER | Named-entity recognition | batch_69e4b29e47a88190be58b79c73d3e652 |
completed | April 19, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69e3f90039e4819080527f860dca042e |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:23 a.m.