Triple
T26864815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rotes Kloster |
E676435
|
entity |
| Predicate | späterGenutztVon |
P6937
|
FINISHED |
| Object | Kamaldulenser |
—
|
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: Kamaldulenser | Statement: [Rotes Kloster, späterGenutztVon, Kamaldulenser]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: späterGenutztVon Context triple: [Rotes Kloster, späterGenutztVon, Kamaldulenser]
-
A.
laterUsedBy
chosen
Indicates that something is subsequently utilized or employed by a specified entity at a later time.
-
B.
areUsedBy
Indicates that certain entities serve as tools, resources, or means that are utilized or employed by other entities.
-
C.
wasUsedBy
Indicates that something served as a tool, resource, or means for an agent to perform an action or achieve a result.
-
D.
usedByFor
Indicates that one entity makes use of another entity for a specific purpose or function.
-
E.
formerlyUsedBy
Indicates that an entity was used by another entity in the past but is no longer in use by that entity.
- 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.