Triple
T37248895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Einführung des Ewigen Landfriedens |
E923936
|
entity |
| Predicate | hatKurzbezeichnung |
P25216
|
FINISHED |
| Object | Ewiger Landfriede |
—
|
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: Ewiger Landfriede | Statement: [Einführung des Ewigen Landfriedens, hatKurzbezeichnung, Ewiger Landfriede]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hatKurzbezeichnung Context triple: [Einführung des Ewigen Landfriedens, hatKurzbezeichnung, Ewiger Landfriede]
-
A.
hatAmtsbezeichnungIn
Indicates that an entity holds or is associated with a specific official title or designation within a given context.
-
B.
hatTeil
Indicates that something is a part or component of something else.
-
C.
hatBezugZu
Indicates that one entity has a (often contextual or referential) relation or connection to another entity.
-
D.
hatCharakter
Indicates that an entity possesses or exhibits a particular character, trait, or quality.
-
E.
bearerShortName
chosen
Indicates that an entity serves as the short or abbreviated name used to identify the bearer in the context of a relationship or action.
- 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_69f76eaabb4c819093b751b139dad551 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb4134225081909fd60703b8cae397 |
completed | May 6, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69fb35bf767081908de8345358ca7f44 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.