Triple
T21807367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | III Rzesza |
E538382
|
entity |
| Predicate | dataUpadku |
P145722
|
FINISHED |
| Object | 1945-05-08 |
—
|
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: 1945-05-08 | Statement: [III Rzesza, dataUpadku, 1945-05-08]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataUpadku Context triple: [III Rzesza, dataUpadku, 1945-05-08]
-
A.
updated
Indicates that an entity has been modified or brought to a more recent state compared to its previous version or status.
-
B.
dataRefresh
Indicates that data is being updated or reloaded to reflect the most current available information.
-
C.
updatesFrom
Indicates that one entity is revised, modified, or brought to a newer state based on information, changes, or content originating from another entity.
-
D.
updatableVia
Indicates that one entity can be modified, refreshed, or brought up to date through the use, action, or mediation of another entity.
-
E.
updatedIn
Indicates that an entity has undergone a change or modification within a specified time period or version context.
- 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_69e0c473f0f8819086c9d1b4a143bd67 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f07803b4888190af06bf7a90198f60 |
completed | April 28, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69e6be751ce881909badced245ef76c7 |
completed | April 21, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69e6c3a2898881909748935cf92f898c |
completed | April 21, 2026, 12:24 a.m. |
Created at: April 16, 2026, 6:53 p.m.