Triple
T9875115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pechenegs |
E240053
|
entity |
| Predicate | warfareStyle |
P709
|
FINISHED |
| Object | horse archery |
—
|
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: horse archery | Statement: [Pechenegs, warfareStyle, horse archery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: warfareStyle Context triple: [Pechenegs, warfareStyle, horse archery]
-
A.
warfareType
Indicates the specific kind or category of warfare that characterizes a given conflict or military engagement.
-
B.
usedWarfareType
chosen
Indicates the specific type or method of warfare that an entity employed in a conflict or military context.
-
C.
warCustom
Indicates a relationship in which one party engages in or applies a particular war-related practice, norm, or customary way of conducting warfare toward or involving another.
-
D.
tacticalStyle
Indicates the characteristic way in which an entity plans and executes actions or maneuvers to achieve its objectives.
-
E.
warLegacy
Indicates that a past war has left lasting impacts or consequences on an entity, such as social, political, economic, or cultural effects that persist over time.
- 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_69ca84e8a0788190b9061811d50fd554 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb3f9d82c81908afb4977ce4e3e4a |
completed | April 2, 2026, 12:10 a.m. |
| PD | Predicate disambiguation | batch_69cd1d7621d48190aa6a6f34399514b0 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:37 p.m.