Triple
T23265579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Länder |
E588135
|
entity |
| Predicate | canBeMergedOrRedefinedBy |
P28179
|
FINISHED |
| Object | federal law with popular consent |
—
|
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: federal law with popular consent | Statement: [Länder, canBeMergedOrRedefinedBy, federal law with popular consent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeMergedOrRedefinedBy Context triple: [Länder, canBeMergedOrRedefinedBy, federal law with popular consent]
-
A.
canMerge
Indicates that two or more entities are compatible in such a way that they can be combined into a single unified entity or structure.
-
B.
wasRedefinedIn
Indicates that an existing entity or concept was modified, updated, or given a new definition at a particular time or in a specific context.
-
C.
mergerImplemented
Indicates that a planned merger between entities has been fully executed and put into effect.
-
D.
canBeDefinedFor
Indicates that a certain concept, operation, or property is applicable to and can be meaningfully specified for a given entity or set of entities.
-
E.
mayBeReplacedBy
chosen
Indicates that one entity can potentially be substituted or superseded by another 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_69e25d148adc819088efbf42672604e9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f194cc3b908190aaefd036aa2b52b5 |
completed | April 29, 2026, 5:19 a.m. |
| PD | Predicate disambiguation | batch_69effce4d704819092826931d430e8c4 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:34 p.m.