Triple
T10822876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Port Republic |
E255418
|
entity |
| Predicate | artilleryCapturedApprox |
P95925
|
FINISHED |
| Object | 9 Union guns |
—
|
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: 9 Union guns | Statement: [Battle of Port Republic, artilleryCapturedApprox, 9 Union guns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: artilleryCapturedApprox Context triple: [Battle of Port Republic, artilleryCapturedApprox, 9 Union guns]
-
A.
artilleryUsedBy
Indicates that a particular artillery asset is operated or employed by a specified user, such as a military unit, organization, or country.
-
B.
artilleryUsedIn
Indicates that a particular piece or type of artillery is employed or deployed in a specific event, operation, or context.
-
C.
artillerySource
Indicates that one entity serves as the origin or launching point from which artillery fire or munitions are deployed toward another entity or location.
-
D.
artilleryType
Indicates the specific category or kind of artillery associated with an entity or event.
-
E.
artilleryUsedFor
Indicates that artillery is employed or utilized for a particular purpose, function, or objective.
- 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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7344c551c8190a7491d468b8a4a04 |
completed | April 9, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_69d70d1bf3648190b36fa96ea018e0dc |
completed | April 9, 2026, 2:21 a.m. |
| PDg | Predicate description generation | batch_69d7101c96708190808fef73199e8482 |
completed | April 9, 2026, 2:34 a.m. |
Created at: April 8, 2026, 9:18 p.m.