Triple
T34108699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Saladen |
E874777
|
entity |
| Predicate | hasCommanderForCombatant1 |
P203419
|
FINISHED |
| Object | Jan Karol Chodkiewicz |
E249148
|
NE 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: Jan Karol Chodkiewicz | Statement: [Battle of Saladen, hasCommanderForCombatant1, Jan Karol Chodkiewicz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommanderForCombatant1 Context triple: [Battle of Saladen, hasCommanderForCombatant1, Jan Karol Chodkiewicz]
-
A.
hasCommander
Indicates that one entity serves as the commanding officer or leader of another entity.
-
B.
hasCommandersFrom
Indicates that an entity has commanders who originate from or are associated with a specified source entity (such as a country, organization, or group).
-
C.
hasCommandant
Indicates that an entity is under the authority or leadership of a specific commandant.
-
D.
hasCommanderOnSide
chosen
Indicates that a particular side or faction is under the command or leadership of a specified commander.
-
E.
hasCommanderRank
Indicates that an entity holds the military or organizational rank of commander within a specified hierarchy or context.
- F. None of above.
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_69f349a80d4481908527317d43f5c579 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3819bc913c8190b9622ba8cb3cf862 |
completed | June 21, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:53 a.m.