Triple
T26084695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Campo Tenese |
E657945
|
entity |
| Predicate | NeapolitanForceType |
P158955
|
FINISHED |
| Object | royal Neapolitan army |
—
|
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: royal Neapolitan army | Statement: [Battle of Campo Tenese, NeapolitanForceType, royal Neapolitan army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NeapolitanForceType Context triple: [Battle of Campo Tenese, NeapolitanForceType, royal Neapolitan army]
-
A.
forzaBelligerante
chosen
Indicates a party’s status or role as a belligerent force engaged in a conflict or war.
-
B.
ParthianForceType
Indicates the type or classification of a military force associated with the Parthians.
-
C.
enemyForceType
Indicates that one entity is characterized as a hostile or opposing force of a specified type relative to another entity.
-
D.
patriotForceType
Indicates the type or category of force associated with a patriot or patriotic group (e.g., military, paramilitary, civilian).
-
E.
besiegingForce
Indicates a military group that is surrounding and attacking a target location or force in an attempt to capture or subdue it.
- 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_69ee5bbf0d208190801ee95d4f07fb16 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f606ff5eb88190bd0390fd9cf1e38d |
completed | May 2, 2026, 2:15 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 7:41 p.m.