Triple
T16522593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | omnium |
E401354
|
entity |
| Predicate | pointAllocationMethod |
P123880
|
FINISHED |
| Object | finishing position in each event |
—
|
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: finishing position in each event | Statement: [omnium, pointAllocationMethod, finishing position in each event]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pointAllocationMethod Context triple: [omnium, pointAllocationMethod, finishing position in each event]
-
A.
winnerSelectionMethod
Indicates the process or criteria used to determine which participant is chosen as the winner.
-
B.
regionalSeatAllocationMethod
Indicates the method or rule used to allocate seats within a specific region.
-
C.
pointsSystemManagedBy
Indicates that the points system is overseen, controlled, or administered by a specified managing entity.
-
D.
weightingMethod
Indicates how relative importance or influence is assigned to elements within a set, such as criteria, features, or data points, in a calculation or decision process.
-
E.
scoreAssignment
Indicates evaluating and assigning a grade or numerical score to an assignment.
- 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e8158cc8190aa77c6d37bd7ec76 |
completed | April 18, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69e296995d388190b88ebe189dce890d |
completed | April 17, 2026, 8:22 p.m. |
| PDg | Predicate description generation | batch_69e2d7f97e548190a474691a152bd8e8 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:14 a.m.