Triple
T3657696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liège–Bastogne–Liège |
E77572
|
entity |
| Predicate | firstEditionCategory |
P50753
|
FINISHED |
| Object | amateur 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: amateur race | Statement: [Liège–Bastogne–Liège, firstEditionCategory, amateur race]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstEditionCategory Context triple: [Liège–Bastogne–Liège, firstEditionCategory, amateur race]
-
A.
firstEditionType
Indicates that an entity is classified as a first edition of a work, specifying the type or category of that first edition.
-
B.
firstEditionMediaType
Indicates the type or format of the medium in which something was originally published in its first edition.
-
C.
firstEditionVolumes
Indicates that the subject is a work or publication and the object is the number of volumes in its first edition.
-
D.
firstEditionFocus
Indicates that the primary emphasis or subject of something is its first edition.
-
E.
firstEditionResult
Indicates that one entity is the outcome, record, or result associated specifically with the first edition of another entity.
- 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_69ad85def5cc8190863dccf55a18bebb |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3d36c1c8190920397a75de4c47d |
completed | March 8, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69adb84650148190bf79231105e58d7f |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adbae14d488190a6024548979c6faf |
completed | March 8, 2026, 6:07 p.m. |
Created at: March 8, 2026, 3:24 p.m.