Triple
T18141378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Aberdeen (1644) |
E434271
|
entity |
| Predicate | combatantForceType |
P6154
|
FINISHED |
| Object | Royalist Irish infantry |
—
|
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: Royalist Irish infantry | Statement: [Battle of Aberdeen (1644), combatantForceType, Royalist Irish infantry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatantForceType Context triple: [Battle of Aberdeen (1644), combatantForceType, Royalist Irish infantry]
-
A.
enemyForceType
Indicates that one entity is characterized as a hostile or opposing force of a specified type relative to another entity.
-
B.
UnionForcesType
Indicates that one entity is associated with, composed of, or characterized by a specific type or category of union forces.
-
C.
USForceType
Indicates the type or category of U.S. military force involved in a given relationship or action.
-
D.
involvedForcesType
Indicates the type or category of forces that participate in or are associated with a given event, interaction, or situation.
-
E.
typeOfTroops
chosen
Indicates the specific category or kind of military forces involved in or associated with an entity or event.
- 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_69d8b90aac308190801e2c57d8c5bfe5 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4de0b67308190ae3be2dbff99910a |
completed | April 19, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69e43317d11c81908d1dc14921566b47 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:29 a.m.