Triple
T27957422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landesminister |
E703588
|
entity |
| Predicate | unterscheidetSichVon |
P6335
|
FINISHED |
| Object | Bundesminister |
—
|
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: Bundesminister | Statement: [Landesminister, unterscheidetSichVon, Bundesminister]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unterscheidetSichVon Context triple: [Landesminister, unterscheidetSichVon, Bundesminister]
-
A.
differIn
Indicates that two entities are not the same in at least one specified aspect, attribute, or value.
-
B.
distinction
Indicates that one entity is recognized, treated, or classified as different or separate from another.
-
C.
differentiatedFrom
chosen
Indicates that one entity is distinguished or set apart from another by identifying differences between them.
-
D.
mechanicallyDistinctFrom
Indicates that two entities differ in their mechanical properties, structure, or behavior such that they are not mechanically equivalent or interchangeable.
-
E.
isDistinctFrom
Indicates that two entities are not identical and can be clearly distinguished from one another.
- 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_69ef840c8b2c8190946ae9522774ba51 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6895f0819088655277e45859a8 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 7:29 p.m.