Triple
T26864814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rotes Kloster |
E676435
|
entity |
| Predicate | Klosterorden |
P99929
|
FINISHED |
| Object | Kartäuserorden |
—
|
NE NERFINISHED |
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: Kartäuserorden | Statement: [Rotes Kloster, Klosterorden, Kartäuserorden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Klosterorden Context triple: [Rotes Kloster, Klosterorden, Kartäuserorden]
-
A.
monasteryOrder
chosen
Indicates that a monastery belongs to, follows, or is affiliated with a particular religious order.
-
B.
founderOfOrder
Indicates that an entity established or created a particular order, organization, or structured group.
-
C.
monasticRepublic
Indicates a relationship where a territory or community is governed as a self-administered monastic state, combining religious monastic rule with a form of republican self-governance.
-
D.
religiousOrderName
Indicates the specific name of the religious order with which an entity is affiliated or associated.
-
E.
notableTempleOrder
Indicates that there is a significant or historically important association between a temple and a particular religious order or monastic lineage.
- 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_69eee9ba94bc8190b44c5d4397d04ecd |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61e96d45881909f2b93dfc522064f |
completed | May 2, 2026, 3:56 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 5:28 a.m.