Triple
T28937051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liebfrauenkirche Koblenz |
E730345
|
entity |
| Predicate | developedAsParishChurchFrom |
P84150
|
FINISHED |
| Object | 12th century |
—
|
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: 12th century | Statement: [Liebfrauenkirche Koblenz, developedAsParishChurchFrom, 12th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedAsParishChurchFrom Context triple: [Liebfrauenkirche Koblenz, developedAsParishChurchFrom, 12th century]
-
A.
isParishChurch
Indicates that a church holds the official status of the main church serving a particular parish within an ecclesiastical jurisdiction.
-
B.
usedAsChurchFrom
chosen
Indicates that something functioned or was utilized as a church starting from a specified point in time.
-
C.
parishChurchCompletedIn
Indicates the year or time period when a specific parish church was completed or finished being built.
-
D.
parishEstablished
Indicates that a parish was formally created or founded at a specific time or under specific authority.
-
E.
isParishChurchIn
Indicates that a church serves as the designated parish church for a specific parish or locality.
- 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_69f043ea0aa88190a25acbf46157995a |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 28, 2026, 8:33 a.m.