Triple
T14478065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paris–Nice 1960 |
E359025
|
entity |
| Predicate | inCompetition |
P35643
|
FINISHED |
| Object | 1960 professional road cycling season |
—
|
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: 1960 professional road cycling season | Statement: [Paris–Nice 1960, inCompetition, 1960 professional road cycling season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inCompetition Context triple: [Paris–Nice 1960, inCompetition, 1960 professional road cycling season]
-
A.
competitionOf
Indicates a relationship where one entity is the competitive event, contest, or rivalry involving another entity.
-
B.
competitionFrom
Indicates that one entity is experiencing competitive pressure or rivalry originating from another entity.
-
C.
competeIn
Indicates that an entity takes part as a contender in a particular event, activity, or domain where performance is compared against others.
-
D.
competitionElement
chosen
Indicates that one entity is a component, phase, or sub-event within a larger competitive event or contest.
-
E.
competitionUse
Indicates that one entity uses or engages in a competition involving another entity.
- 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_69d827966698819082e140837737501d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de9248edb48190a74eb032aeaac027 |
completed | April 14, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c487b4c819097803e58dca628a5 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:20 a.m.