Triple
T9875114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pechenegs |
E240053
|
entity |
| Predicate | primaryMilitaryArm |
P78511
|
FINISHED |
| Object | cavalry |
—
|
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: cavalry | Statement: [Pechenegs, primaryMilitaryArm, cavalry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryMilitaryArm Context triple: [Pechenegs, primaryMilitaryArm, cavalry]
-
A.
countryMilitary
Indicates that a country possesses, controls, or is associated with a particular military force or armed organization.
-
B.
militarySystem
Indicates a relationship where an entity functions as, belongs to, or is characterized by a particular military organizational or operational system.
-
C.
primaryArms
chosen
Indicates that the subject possesses or uses the specified arms or weapons as its main or most important set.
-
D.
militaryBranchOfGovernment
Indicates that a military organization functions as an official branch or component of a government.
-
E.
militaryOrganization
Indicates that an entity functions as, or is associated with, a structured armed forces or defense-related organization.
- 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.