Triple
T18151903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schlacht bei Kay |
E434523
|
entity |
| Predicate | VorgängerEreignis |
P25144
|
FINISHED |
| Object | Russischer Feldzug 1759 in der Neumark |
—
|
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: Russischer Feldzug 1759 in der Neumark | Statement: [Schlacht bei Kay, VorgängerEreignis, Russischer Feldzug 1759 in der Neumark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: VorgängerEreignis Context triple: [Schlacht bei Kay, VorgängerEreignis, Russischer Feldzug 1759 in der Neumark]
-
A.
predecessor
Indicates that one entity comes before another in an ordered sequence or succession.
-
B.
predecessorSeries
Indicates that one series directly precedes another in an ordered sequence or lineage.
-
C.
predecessorCampaign
Indicates that one campaign directly precedes another in a sequence or lifecycle.
-
D.
wasPrecededBy
chosen
Indicates that one event, state, or entity occurred or existed earlier in time than another.
-
E.
predecessorProject
Indicates that one project temporally or logically comes before and leads into another project in a sequence or dependency chain.
- 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_69d8b90aac308190801e2c57d8c5bfe5 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4de38d4e08190bc4d430b70b7e288 |
completed | April 19, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69e43317d11c81908d1dc14921566b47 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:29 a.m.