Triple
T28351431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishopric of Naumburg-Zeitz |
E718108
|
entity |
| Predicate | foundedForMissionAmong |
P118121
|
FINISHED |
| Object | Slavic populations east of the Saale |
—
|
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: Slavic populations east of the Saale | Statement: [Bishopric of Naumburg-Zeitz, foundedForMissionAmong, Slavic populations east of the Saale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedForMissionAmong Context triple: [Bishopric of Naumburg-Zeitz, foundedForMissionAmong, Slavic populations east of the Saale]
-
A.
establishedMissionFor
Indicates that an entity formally created or set up a specific mission, assigning it purpose or objectives.
-
B.
foundedAsMissionFor
chosen
Indicates that one entity was originally established as a mission specifically intended to serve or support another entity.
-
C.
foundedFor
Indicates that an entity was established or created specifically to serve, support, or benefit another entity or purpose.
-
D.
foundedWith
Indicates that an entity was established or created together with another entity, typically as co-founders or jointly initiated partners.
-
E.
namedForMission
Indicates that something (such as an object, place, or project) is given a name in honor of or derived from a particular mission.
- 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_69eff6ec27b481908c8d7b86c47893d9 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: April 28, 2026, 12:46 a.m.