Triple
T31341122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omloop Het Nieuwsblad |
E799307
|
entity |
| Predicate | startList |
P199193
|
FINISHED |
| Object | UCI WorldTeams |
—
|
NE NERFINISHED |
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 WorldTeams | Statement: [Omloop Het Nieuwsblad, startList, UCI WorldTeams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startList Context triple: [Omloop Het Nieuwsblad, startList, UCI WorldTeams]
-
A.
startsAs
Indicates that an entity initially exists or appears in a particular form, state, or role before potentially changing to another.
-
B.
startTrigger
Indicates that one event, condition, or action initiates or causes the beginning of another.
-
C.
exportStart
Indicates the point in time or event at which an export process or outbound transfer of goods, data, or resources begins.
-
D.
startRule
Indicates that a particular rule is the initial or entry rule from which a process, system, or evaluation begins.
-
E.
startPoint
Indicates the initial location or position from which an object, path, or action begins.
- 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_69f224e3f6ac8190a13488516abca7c9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff255b84788190a94682f4efe1d0b8 |
completed | May 9, 2026, 12:15 p.m. |
| PD | Predicate disambiguation | batch_69ff24f3ab108190bb017a656cff3d82 |
completed | May 9, 2026, 12:13 p.m. |
| PDg | Predicate description generation | batch_69ff255abca881908ef7635bd2e5af98 |
completed | May 9, 2026, 12:15 p.m. |
Created at: April 29, 2026, 9:16 p.m.