Triple
T37744663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DBK |
E940813
|
entity |
| Predicate | isAssemblyOf |
P188990
|
FINISHED |
| Object | Catholic bishops in Germany |
—
|
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: Catholic bishops in Germany | Statement: [DBK, isAssemblyOf, Catholic bishops in Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAssemblyOf Context triple: [DBK, isAssemblyOf, Catholic bishops in Germany]
-
A.
hasAssembly
Indicates that an entity is composed of, or includes, one or more component parts assembled into a whole.
-
B.
issAssemblySequence
Indicates that one entity specifies the ordered sequence of assembly steps or components required to construct another entity.
-
C.
coreAssembly
Indicates that an entity is responsible for assembling or integrating the central or primary components of another entity into a complete core unit.
-
D.
isAComponentOf
Indicates that one entity functions as a constituent part or sub-unit of another, larger entity.
-
E.
involvedInComplexAssembly
Indicates that an entity participates in the process of assembling or forming a larger molecular or structural complex.
- F. None of above. chosen
Provenance (4 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_69f76ee0e32c8190b40a3b4cf590337c |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaf48ba148190a8bdfd6846ad0540 |
completed | May 6, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69fbadf632ec8190b14991c971258307 |
completed | May 6, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69fbaeef9c488190babb546b962b4fb6 |
completed | May 6, 2026, 9:13 p.m. |
Created at: May 3, 2026, 4:19 p.m.