Triple
T553607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Ramillies |
E11894
|
entity |
| Predicate | capturedGuns |
P14511
|
FINISHED |
| Object | over 50 artillery pieces (approximate) |
—
|
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: over 50 artillery pieces (approximate) | Statement: [Battle of Ramillies, capturedGuns, over 50 artillery pieces (approximate)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capturedGuns Context triple: [Battle of Ramillies, capturedGuns, over 50 artillery pieces (approximate)]
-
A.
capturedEquipment
chosen
Indicates that one party has taken possession of another party’s equipment, typically as a result of conflict, competition, or enforcement.
-
B.
weaponsUsed
Indicates that one entity employed or utilized another entity as a weapon in carrying out an action or event.
-
C.
gunType
Indicates the specific category or kind of gun associated with an entity.
-
D.
gun
Indicates that one entity uses, carries, or is associated with a gun in relation to another entity or context.
-
E.
gunCalibre
Indicates the relationship between a firearm and the calibre (size/diameter) of ammunition it is designed to use.
- 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_69a4932941d08190815efd422f0b4ca7 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4991b296481908cf27e1d1ec67052 |
completed | March 1, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69a494bc1f8c8190904356f3a8e801de |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.