Triple
T10204091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mainz Cathedral |
E238958
|
entity |
| Predicate | sharedUseWith |
P2507
|
FINISHED |
| Object | regional Protestant congregations |
—
|
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: regional Protestant congregations | Statement: [Mainz Cathedral, sharedUseWith, regional Protestant congregations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharedUseWith Context triple: [Mainz Cathedral, sharedUseWith, regional Protestant congregations]
-
A.
usedWith
Indicates that one entity is typically or appropriately employed together with another entity in a combined or complementary use.
-
B.
sharesFieldWith
Indicates that two entities are involved in or associated with the same field, discipline, or area of specialization.
-
C.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
-
D.
isSharedBy
chosen
Indicates that something is jointly possessed, used, or experienced by two or more entities.
-
E.
sharesBaseWith
Indicates that two entities have a common underlying base element, source, or component from which they are derived or constructed.
- 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_69ca84e1ea088190b38162e43d4cfa8f |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdeed6fd0081908f8afad1ef4c6bff |
completed | April 2, 2026, 4:21 a.m. |
| PD | Predicate disambiguation | batch_69cd7c8b7f348190a585daa70de4d4c8 |
completed | April 1, 2026, 8:14 p.m. |
Created at: March 30, 2026, 9:14 p.m.