Triple
T2018858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samnites |
E44057
|
entity |
| Predicate | militaryEquipment |
P6496
|
FINISHED |
| Object | oval shield |
—
|
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: oval shield | Statement: [Samnites, militaryEquipment, oval shield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryEquipment Context triple: [Samnites, militaryEquipment, oval shield]
-
A.
militaryTechnology
chosen
Indicates that one entity is a type of military-related technology used for defense, combat, or warfare purposes.
-
B.
militaryUse
Indicates the use of something (such as land, facilities, equipment, or resources) for military purposes or operations.
-
C.
militaryEquivalence
Indicates that two or more entities possess comparable military capabilities, strength, or strategic power such that neither holds a clear military advantage over the other.
-
D.
militaryProject
Indicates a project that is conducted, funded, or controlled by a military organization, typically for defense, security, or warfare-related purposes.
-
E.
militaryDomain
Indicates that the relationship or action occurs within, pertains to, or is specifically associated with the military sphere or 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_69a8891201bc8190aca837be6de41579 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb8cfa5c88190b55bce5db968665b |
completed | March 7, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69abb7a389408190a84a54856352f15b |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:38 p.m.