Triple
T22273729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aberavon RFC |
E550546
|
entity |
| Predicate | traditionalCompetitionLevel |
P18266
|
FINISHED |
| Object | top tier of Welsh club rugby |
—
|
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: top tier of Welsh club rugby | Statement: [Aberavon RFC, traditionalCompetitionLevel, top tier of Welsh club rugby]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalCompetitionLevel Context triple: [Aberavon RFC, traditionalCompetitionLevel, top tier of Welsh club rugby]
-
A.
primaryCompetitionLevel
chosen
Indicates the main or highest level of competition at which an entity primarily competes or operates.
-
B.
levelOfCompetitionAdministered
Indicates the specific competitive tier or intensity at which an activity, event, or process is formally managed or overseen.
-
C.
competitionLevel
Indicates the degree or intensity of competitive pressure or rivalry present in a given context or interaction.
-
D.
levelOfCompetition
Indicates the intensity or degree of competitive pressure present in a given context or interaction.
-
E.
competitionLevelOf
Indicates the degree or intensity of competitiveness associated with an entity, event, 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_69e11e43d8208190aff4f9cf7f2c2a8a |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f14ea547e4819098baf88f3c605242 |
completed | April 29, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e72ff0363081909f794d19c8a64837 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:40 p.m.