Triple
T16816654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Dubienka |
E408768
|
entity |
| Predicate | strengthPolish |
P6664
|
FINISHED |
| Object | approximately 5,300 soldiers |
—
|
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: approximately 5,300 soldiers | Statement: [Battle of Dubienka, strengthPolish, approximately 5,300 soldiers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strengthPolish Context triple: [Battle of Dubienka, strengthPolish, approximately 5,300 soldiers]
-
A.
strength
chosen
Indicates the degree of power, intensity, or effectiveness with which an entity can act on, influence, or withstand another entity or force.
-
B.
PolishObjective
Indicates that an entity is the target or goal of a polishing action or process.
-
C.
polishUnit
Indicates that one entity performs the action of polishing or refining another entity, typically improving its surface, appearance, or quality.
-
D.
strengthDescription
Indicates a description or characterization of the degree of strength associated with an entity or relationship.
-
E.
strengthType
Indicates the specific category or nature of strength associated with an entity or relationship (e.g., physical, structural, or conceptual strength).
- 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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b2e1de908190aa3508770fb865cf |
completed | April 18, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69e32b814b188190aee525f8779203cd |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.