Triple
T10204092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mainz Cathedral |
E238958
|
entity |
| Predicate | sharedUseType |
P2507
|
FINISHED |
| Object | interdenominational use |
—
|
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: interdenominational use | Statement: [Mainz Cathedral, sharedUseType, interdenominational use]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharedUseType Context triple: [Mainz Cathedral, sharedUseType, interdenominational use]
-
A.
sharesSystemWith
Indicates that two entities operate within or are associated with the same overarching system or environment.
-
B.
sharesAreaWith
Indicates that two entities occupy or overlap the same geographic or spatial area.
-
C.
sharesElementsWith
Indicates that two entities have one or more elements or components in common.
-
D.
isSharedBy
chosen
Indicates that something is jointly possessed, used, or experienced by two or more entities.
-
E.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
- 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.