Triple
T22170594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Longsword |
E547909
|
entity |
| Predicate | usedInCombatType |
P98669
|
FINISHED |
| Object | armored combat |
—
|
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: armored combat | Statement: [Longsword, usedInCombatType, armored combat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInCombatType Context triple: [Longsword, usedInCombatType, armored combat]
-
A.
hasCombatType
chosen
Indicates that an entity is associated with a particular mode or category of combat it uses or participates in.
-
B.
usesCombatSystem
Indicates that one entity employs or operates a particular combat system in its functioning or behavior.
-
C.
usedInBattle
Indicates that something (typically a tool, strategy, or resource) was employed or applied during a battle or combat situation.
-
D.
hasCombat
Indicates that an entity engages in, is involved with, or possesses the capability for combat or fighting interactions with other entities.
-
E.
usedWarfareType
Indicates the specific type or method of warfare that an entity employed in a conflict or military context.
- 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_69e11e3c4c5c81908d336165816b12e0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12a67f4dc81909cc5f8d2c1fe6129 |
completed | April 28, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69e71b41555881909b8e22718974d527 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:34 p.m.