Triple
T35917333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rally of the Thousand Lakes |
E1038782
|
entity |
| Predicate | hasServiceParkLocation |
P55814
|
FINISHED |
| Object | Jyväskylä |
—
|
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: Jyväskylä | Statement: [Rally of the Thousand Lakes, hasServiceParkLocation, Jyväskylä]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasServiceParkLocation Context triple: [Rally of the Thousand Lakes, hasServiceParkLocation, Jyväskylä]
-
A.
hasParkServiceSign
Indicates that an entity features or is marked by an official park service sign.
-
B.
servicePark
chosen
Indicates that one entity serves as a designated area or facility where vehicles or equipment are parked, maintained, or serviced in relation to another entity.
-
C.
parkServed
Indicates that a particular park is provided with services or coverage by a specified entity (such as a transit line, facility, or administrative body).
-
D.
hasParkingFor
Indicates that a place or facility provides designated parking spaces suitable for a specified type of vehicle or user.
-
E.
hasParking
Indicates that a place or facility provides designated parking space(s) available for use.
- 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_69f76e2320748190b7f5c4750d0cd0d3 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a002f0839fc8190a874d3b0d0826d7e |
completed | May 10, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_6a002eae7b6481909974b321e2789b7e |
completed | May 10, 2026, 7:07 a.m. |
Created at: May 3, 2026, 4:07 p.m.