Triple
T15923447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UCI Class 1 race |
E386147
|
entity |
| Predicate | competitionTierAbove |
P98882
|
FINISHED |
| Object | UCI Class 2 race |
—
|
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: UCI Class 2 race | Statement: [UCI Class 1 race, competitionTierAbove, UCI Class 2 race]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competitionTierAbove Context triple: [UCI Class 1 race, competitionTierAbove, UCI Class 2 race]
-
A.
competitionLevel
Indicates the degree or intensity of competitive pressure or rivalry present in a given context or interaction.
-
B.
competitionLevelOf
Indicates the degree or intensity of competitiveness associated with an entity, event, or context.
-
C.
aboveCompetition
chosen
Indicates that one entity is positioned higher than another within a competitive ranking or hierarchy.
-
D.
competitionHierarchyLevel
Indicates the relative rank or tier of a competition within an overall competitive structure or hierarchy.
-
E.
primaryCompetitionLevel
Indicates the main or highest level of competition at which an entity primarily competes or operates.
- 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_69d86da750008190987eb26be3f6c118 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e172b48b308190bc430b2308cbc75b |
completed | April 16, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69e142cf5c548190a931f7b58144cd31 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:52 a.m.