Triple
T34985408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Synod of the Church of Sweden |
E1008930
|
entity |
| Predicate | countryOfMeeting |
P96055
|
FINISHED |
| Object | Sweden |
E7489
|
NE 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: Sweden | Statement: [General Synod of the Church of Sweden, countryOfMeeting, Sweden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryOfMeeting Context triple: [General Synod of the Church of Sweden, countryOfMeeting, Sweden]
-
A.
countryOfInteraction
chosen
Indicates that an interaction, event, or relationship took place within, or is associated with, a specific country.
-
B.
countryOfVenue
Indicates the country in which the referenced venue is geographically located.
-
C.
locationCountryOfCeremony
Indicates the country in which a particular ceremony takes place or is held.
-
D.
meetsInCountry
Indicates that two or more entities have an in-person meeting that takes place within the specified country.
-
E.
meetsCountriesAt
Indicates that two or more entities (typically borders or regions) come together or intersect at a location associated with specific countries.
- F. None of above.
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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a019b8995dc819088727aa023beadce |
completed | May 11, 2026, 9:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37b26447cc8190a75dcc83b3110ef5 |
completed | June 21, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_6a01961bb748819096a941f1b5443908 |
completed | May 11, 2026, 8:40 a.m. |
Created at: May 3, 2026, 4:01 p.m.