Triple
T36340842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of La Rothière (1814) |
E894915
|
entity |
| Predicate | AlliedArtilleryApprox |
P110014
|
FINISHED |
| Object | about 200 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: about 200 guns | Statement: [Battle of La Rothière (1814), AlliedArtilleryApprox, about 200 guns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AlliedArtilleryApprox Context triple: [Battle of La Rothière (1814), AlliedArtilleryApprox, about 200 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.
troopStrengthAlliedApprox
Indicates that the approximate troop strength of one entity is being assessed or reported in relation to its allied forces.
-
C.
artilleryPiecesUsed
chosen
Indicates that certain artillery pieces were employed or deployed in a particular action, event, or context.
-
D.
artillerySupport
Indicates that one entity provides or coordinates artillery fire in support of another entity’s operations or objectives.
-
E.
artilleryWeight
Indicates the weight or mass associated with a piece of artillery in the relationship.
- 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_69f76e4e90148190b02fe52593c70b5b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7bb3ff1b08190802b1063d55d3923 |
completed | May 3, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a611a081908dd6aec1df3f4d7f |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:09 p.m.