Triple
T527900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wales Conference All-Stars |
E10962
|
entity |
| Predicate | hasCompetitionScope |
P15208
|
FINISHED |
| Object | league-wide |
—
|
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: league-wide | Statement: [Wales Conference All-Stars, hasCompetitionScope, league-wide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompetitionScope Context triple: [Wales Conference All-Stars, hasCompetitionScope, league-wide]
-
A.
hasCompetition
Indicates that one entity is in a state of rivalry or contest with another entity, typically competing for the same goal, resource, or advantage.
-
B.
appliesToCompetition
Indicates that something (such as a rule, condition, or attribute) is relevant or applicable specifically to a competition.
-
C.
usesCompetitionSystem
Indicates that an entity operates under or applies a particular competition system or format.
-
D.
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).
-
E.
usedInCompetition
Indicates that something is employed or utilized as part of a competition or contest.
- F. None of above. chosen
Provenance (4 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_69a2e84b16c4819088d284c47c3a7968 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1d2851c81908129f7da932ab7b3 |
completed | Feb. 28, 2026, 1:46 p.m. |
| PD | Predicate disambiguation | batch_69a2f01ac3ec8190a94a05955532c7fa |
completed | Feb. 28, 2026, 1:39 p.m. |
| PDg | Predicate description generation | batch_69a2f0dcff1881909c18e8c599c150a1 |
completed | Feb. 28, 2026, 1:42 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.