Triple
T37339278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Col d’Izoard |
E926985
|
entity |
| Predicate | hasGiroRole |
P187743
|
FINISHED |
| Object | occasionally used in the Giro d’Italia |
—
|
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: occasionally used in the Giro d’Italia | Statement: [Col d’Izoard, hasGiroRole, occasionally used in the Giro d’Italia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGiroRole Context triple: [Col d’Izoard, hasGiroRole, occasionally used in the Giro d’Italia]
-
A.
hasGlobalRole
Indicates that an entity holds a role or permission set that applies across an entire system or domain, rather than being limited to a specific scope or context.
-
B.
hasRole
Indicates that an entity occupies, performs, or is assigned a specific role or function in relation to another entity or context.
-
C.
hasGoverningRole
Indicates that one entity holds an official position of authority, control, or governance over another entity or domain.
-
D.
mayHaveRole
Indicates that an entity is permitted or eligible to hold or perform a specified role.
-
E.
hasLegalRole
Indicates that an entity holds a specific legal capacity, status, or function in relation to another entity or context.
- 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_69f76eb4e8a881908bd40da28f36fc7e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb8c38a9688190be524246f5682107 |
completed | May 6, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9c6e0481908565bd849e869b24 |
completed | May 6, 2026, 3:13 p.m. |
| PDg | Predicate description generation | batch_69fb8c37931c81909da038c18ed9add2 |
completed | May 6, 2026, 6:45 p.m. |
Created at: May 3, 2026, 4:16 p.m.