Triple
T32183457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CCI5*-L |
E822043
|
entity |
| Predicate | targetCompetitorLevel |
P180985
|
FINISHED |
| Object | Olympic-caliber riders |
—
|
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: Olympic-caliber riders | Statement: [CCI5*-L, targetCompetitorLevel, Olympic-caliber riders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetCompetitorLevel Context triple: [CCI5*-L, targetCompetitorLevel, Olympic-caliber riders]
-
A.
levelOfCompetition
Indicates the intensity or degree of competitive pressure present in a given context or interaction.
-
B.
targetCompetition
Indicates that one entity is the specific competition or contest that another entity is aiming for, focusing on, or attempting to win.
-
C.
underlyingCompanyMajorCompetitor
Indicates that one company serves as a primary or significant competitor to another company.
-
D.
competitionLevelOf
Indicates the degree or intensity of competitiveness associated with an entity, event, or context.
-
E.
competesAtLevel
chosen
Indicates that one entity participates in competition at a specified level or tier relative to others.
- 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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fde5d7d9548190880a9d95b8f0f66b |
completed | May 8, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69fde4e1bf9c81909754545275eccc03 |
completed | May 8, 2026, 1:28 p.m. |
Created at: May 1, 2026, 12:34 a.m.