Triple
T23212591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Heliopolis (1800) |
E580638
|
entity |
| Predicate | FrenchForceComposition |
P6154
|
FINISHED |
| Object | veteran infantry and artillery units |
—
|
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: veteran infantry and artillery units | Statement: [Battle of Heliopolis (1800), FrenchForceComposition, veteran infantry and artillery units]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FrenchForceComposition Context triple: [Battle of Heliopolis (1800), FrenchForceComposition, veteran infantry and artillery units]
-
A.
USForceStrength
Indicates the level or magnitude of military forces deployed or available by the United States in a given context.
-
B.
FrenchUnit
Indicates that a unit or entity is associated with France, typically by origin, affiliation, or national identity.
-
C.
commandingForceSize
Indicates the size or magnitude of the military or organizational force that is exercising command or control in a given context.
-
D.
USForceType
Indicates the type or category of U.S. military force involved in a given relationship or action.
-
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_69e2460389408190be74f41d217799a9 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f191620378819096362252c3b819b6 |
completed | April 29, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69effcccee508190a7ae311fdd319806 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:07 p.m.