Triple
T14482613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alto de Arkale |
E359147
|
entity |
| Predicate | oftenFeaturesIn |
P3100
|
FINISHED |
| Object | final part of Clásica de San Sebastián |
—
|
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: final part of Clásica de San Sebastián | Statement: [Alto de Arkale, oftenFeaturesIn, final part of Clásica de San Sebastián]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenFeaturesIn Context triple: [Alto de Arkale, oftenFeaturesIn, final part of Clásica de San Sebastián]
-
A.
oftenUse
Indicates that one entity frequently or regularly uses, employs, or utilizes another entity.
-
B.
oftenSays
Indicates that one entity frequently makes a particular statement or remark, or regularly expresses a certain idea or phrase.
-
C.
oftenSoughtOn
Indicates that one entity is frequently searched for, requested, or pursued in relation to another entity.
-
D.
frequentOccasion
Indicates that a particular event, situation, or condition occurs repeatedly or commonly over time.
-
E.
oftenAccompaniedBy
chosen
Indicates that one entity is frequently found together with, occurs alongside, or is commonly associated in presence or use with 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_69de924bc548819087a2f693840d7426 |
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.