Triple
T23724460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ole Herman Johannes Krag |
E586230
|
entity |
| Predicate | weaponUsedIn |
P153717
|
FINISHED |
| Object | late 19th century conflicts |
—
|
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: late 19th century conflicts | Statement: [Ole Herman Johannes Krag, weaponUsedIn, late 19th century conflicts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weaponUsedIn Context triple: [Ole Herman Johannes Krag, weaponUsedIn, late 19th century conflicts]
-
A.
weaponUsedAgainst
Indicates that a particular weapon or instrument is employed in an act of aggression, attack, or harm directed toward a specific target or entity.
-
B.
weaponsUsed
Indicates that one entity employed or utilized another entity as a weapon in carrying out an action or event.
-
C.
usedWeapon
Indicates that an entity employed a specific weapon as the means or tool to carry out an action or event.
-
D.
weapon
Indicates that one entity is used as a weapon by, or serves as the weapon of, another entity.
-
E.
typicalWeapon
Indicates that the object is a weapon commonly or characteristically used by the subject.
- 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_69e24906fb108190a6898751e46bdc11 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b91364208190b3404534a7403e08 |
completed | April 29, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
| PDg | Predicate description generation | batch_69f15b453da88190889a8d9b21727958 |
completed | April 29, 2026, 1:13 a.m. |
Created at: April 17, 2026, 7:07 p.m.