Triple
T9103602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Lodi |
E218418
|
entity |
| Predicate | FrenchForceApproximateStrength |
P24882
|
FINISHED |
| Object | about 20,000 men |
—
|
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 20,000 men | Statement: [Battle of Lodi, FrenchForceApproximateStrength, about 20,000 men]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FrenchForceApproximateStrength Context triple: [Battle of Lodi, FrenchForceApproximateStrength, about 20,000 men]
-
A.
commandingForce2Strength
Indicates that a commanding force possesses or exerts a particular level or measure of strength.
-
B.
commandingForce1Strength
Indicates that one entity has a certain level or measure of strength in its role as the primary commanding force over another entity or situation.
-
C.
UnionForcesStrength
Indicates the level or magnitude of military power possessed by Union forces in a given context.
-
D.
USForceStrength
Indicates the level or magnitude of military forces deployed or available by the United States in a given context.
-
E.
strengthFrance
chosen
Indicates a relationship where a level, measure, or attribute of strength is associated specifically with France.
- 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_69ca83db7448819090d0a5de842ef2ac |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca56f1f10819091abadf7cd06c3a6 |
completed | April 1, 2026, 4:56 a.m. |
| PD | Predicate disambiguation | batch_69cc65fc7f408190a5846e29ab3b97e5 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:15 p.m.