Triple
T29397106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Lidzbark Warmiński |
E745528
|
entity |
| Predicate | RussianPrussianStrengthApprox |
P166731
|
FINISHED |
| Object | 65000 |
—
|
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: 65000 | Statement: [Battle of Lidzbark Warmiński, RussianPrussianStrengthApprox, 65000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RussianPrussianStrengthApprox Context triple: [Battle of Lidzbark Warmiński, RussianPrussianStrengthApprox, 65000]
-
A.
PrussianStrengthApprox
Indicates an approximate assessment or estimation of the strength or power associated with Prussia in a given context.
-
B.
PrussianStrength
Indicates a relationship where an entity possesses or exhibits the military, political, or institutional power characteristic of Prussia.
-
C.
PrussianForceType
Indicates the specific type or classification of a military force associated with Prussia.
-
D.
strengthRussoAustrian
Indicates the relative military or political strength between Russian and Austrian forces or interests in a given context.
-
E.
strengthRussia
Indicates a relationship where a level, measure, or display of strength is attributed to or associated with Russia.
- 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66a0486448190aad3372000e53ebb |
completed | May 2, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f661b47d088190934f63884a203261 |
completed | May 2, 2026, 8:42 p.m. |
Created at: April 28, 2026, 2:47 p.m.