Triple
T281612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basic Law for the Federal Republic of Germany |
E5365
|
entity |
| Predicate | definesStateAs |
P773
|
FINISHED |
| Object | democratic |
—
|
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: democratic | Statement: [Basic Law for the Federal Republic of Germany, definesStateAs, democratic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesStateAs Context triple: [Basic Law for the Federal Republic of Germany, definesStateAs, democratic]
-
A.
defined
chosen
Indicates that one entity specifies, explains, or establishes the meaning, scope, or identity of another entity.
-
B.
associatedState
Indicates that one entity is linked or connected to a particular state, condition, or status of another entity.
-
C.
definedOn
Indicates that something (such as a function, rule, or structure) is specified to apply or be valid over a particular domain, set, or context.
-
D.
stateless
Indicates that an entity does not retain or depend on any internal state between separate interactions or operations.
-
E.
primaryStates
Indicates that certain states or conditions are the main or most fundamental ones within a given context or system.
- 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_69a257e6c8788190987dfe705ca2912a |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25e0a23c0819083abee28b2dea49c |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b77e028819087e606fc321219f7 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:59 a.m.