Triple
T12983329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Bicocca |
E321703
|
entity |
| Predicate | primaryTroopTypeImperialSpanish |
P107887
|
FINISHED |
| Object | Spanish arquebusiers |
—
|
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: Spanish arquebusiers | Statement: [Battle of Bicocca, primaryTroopTypeImperialSpanish, Spanish arquebusiers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryTroopTypeImperialSpanish Context triple: [Battle of Bicocca, primaryTroopTypeImperialSpanish, Spanish arquebusiers]
-
A.
SpanishFleetStrength
Indicates the relative size or power of a Spanish naval fleet in a given context or time.
-
B.
commanderForSpain
Indicates that a person serves or has served as a military commander on behalf of Spain.
-
C.
tacticsUsedBySpanish
Indicates that certain tactics or strategies are employed or carried out by Spanish forces, groups, or individuals.
-
D.
SpanishSquadron
Indicates a relationship where an entity is identified as, or associated with, a naval or military squadron belonging to Spain.
-
E.
obligationsOfSpain
Indicates that certain duties, responsibilities, or commitments are borne by Spain in a given context.
- F. None of above. chosen
Provenance (4 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_69d8076479b8819090afce3591939cdf |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97f2a71a0819098bb6cf8a4b2208a |
completed | April 10, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69d97dbdd94c8190ac4bbecca02dc77b |
completed | April 10, 2026, 10:46 p.m. |
| PDg | Predicate description generation | batch_69d97f1badac8190a59e60751f47b8d6 |
completed | April 10, 2026, 10:52 p.m. |
Created at: April 9, 2026, 8:39 p.m.