Triple
T10042513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Memorial Day of the Fallen in Finland |
E205329
|
entity |
| Predicate | mainCeremoniesLocation |
P128
|
FINISHED |
| Object | local churches in Finland |
—
|
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: local churches in Finland | Statement: [Memorial Day of the Fallen in Finland, mainCeremoniesLocation, local churches in Finland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainCeremoniesLocation Context triple: [Memorial Day of the Fallen in Finland, mainCeremoniesLocation, local churches in Finland]
-
A.
ceremonyLocation
chosen
Indicates the place where a ceremony is held or takes place.
-
B.
ceremonialVenueFunction
Indicates that a venue serves a role or purpose specifically related to hosting or supporting ceremonial events or activities.
-
C.
ceremonyHeld
Indicates that a formal ceremony or ritual event has taken place at a particular time and/or location.
-
D.
ceremonyHeldOn
Indicates that a specific ceremony took place on a particular date or day.
-
E.
ceremonialHeadOffice
Indicates that an entity serves as the official but largely symbolic or ceremonial head office for 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_69ca834f70e88190b2d74828b7767ec1 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcf60a2208190846e57b5f5649307 |
completed | April 2, 2026, 2:07 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8d2280819089de27e57babd1f3 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 8:55 p.m.