Triple
T16914948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman–Etruscan wars |
E410296
|
entity |
| Predicate | militaryCampaignType |
P1403
|
FINISHED |
| Object | land warfare |
—
|
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: land warfare | Statement: [Roman–Etruscan wars, militaryCampaignType, land warfare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryCampaignType Context triple: [Roman–Etruscan wars, militaryCampaignType, land warfare]
-
A.
militaryCampaignOf
Indicates a relationship where a specific military campaign is conducted by, initiated by, or belongs to a particular military force, state, or commander.
-
B.
militaryCampaigns
Indicates that an entity conducts, participates in, or is associated with organized military operations or campaigns against another entity or within a specific conflict.
-
C.
militaryCampaignsIn
Indicates that a military campaign took place within, or was conducted in, a specified geographic or political area.
-
D.
warfareType
chosen
Indicates the specific kind or category of warfare that characterizes a given conflict or military engagement.
-
E.
militaryConflict
Indicates a relationship where two or more parties are engaged in organized, armed hostilities or warfare against each other.
- 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_69d886c7b1e481908c3766dfa8c13458 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3ca4015648190989904ad7119c3be |
completed | April 18, 2026, 6:15 p.m. |
| PD | Predicate disambiguation | batch_69e32b9489408190bcb2ede567ff5bf9 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:30 a.m.