Triple
T13426212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rally Finland |
E313487
|
entity |
| Predicate | hasServicePark |
P55814
|
FINISHED |
| Object | Jyväskylä service park |
—
|
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: Jyväskylä service park | Statement: [Rally Finland, hasServicePark, Jyväskylä service park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasServicePark Context triple: [Rally Finland, hasServicePark, Jyväskylä service park]
-
A.
hasParkServiceSign
Indicates that an entity features or is marked by an official park service sign.
-
B.
hasParkStatus
Indicates that an entity holds a particular designation or status related to being a park (e.g., national park, city park, protected parkland).
-
C.
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.
-
D.
hasParkFeature
Indicates that a park includes, contains, or is associated with a specific feature or amenity.
-
E.
hasParkSection
Indicates that one entity includes, contains, or is associated with a specific section or area of a park.
- 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_69d806ad0c44819088833ae1ec9e9690 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaed066408190a416880affd8416e |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03926188190ab3948d1f5d3941f |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:40 p.m.