Triple
T18151892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schlacht bei Kay |
E434523
|
entity |
| Predicate | BeteiligtePartei |
P93891
|
FINISHED |
| Object | Königreich Preußen |
—
|
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: Königreich Preußen | Statement: [Schlacht bei Kay, BeteiligtePartei, Königreich Preußen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BeteiligtePartei Context triple: [Schlacht bei Kay, BeteiligtePartei, Königreich Preußen]
-
A.
partyOfCandidate
Indicates the political party with which a given candidate is affiliated.
-
B.
partnerInPolitics
Indicates that two entities are political partners, collaborating or aligned in political activities, campaigns, or governance.
-
C.
involvedPoliticalEntity
chosen
Indicates that a political entity participates in, is associated with, or plays a role in a given event, action, or relationship.
-
D.
affectedPoliticalParty
Indicates that a political party is impacted or influenced by a particular event, action, policy, or situation.
-
E.
mainParties
Indicates the primary entities that are directly and centrally involved in a given relationship, event, or agreement.
- 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.