Triple
T5849835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army of the Orient |
E129999
|
entity |
| Predicate | successorForce |
P66717
|
FINISHED |
| Object | French forces under General Jean-Baptiste Kléber |
—
|
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: French forces under General Jean-Baptiste Kléber | Statement: [Army of the Orient, successorForce, French forces under General Jean-Baptiste Kléber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorForce Context triple: [Army of the Orient, successorForce, French forces under General Jean-Baptiste Kléber]
-
A.
successor
Indicates that one entity directly follows another in an ordered sequence or position.
-
B.
successorCampaign
Indicates that one campaign directly follows and continues or replaces another campaign in sequence.
-
C.
successorUse
Indicates that one entity is used or applied as the subsequent or follow-up use of another entity in a sequence or lifecycle.
-
D.
successorSystem
Indicates that one system directly follows and replaces another in function, role, or version.
-
E.
successorControl
Indicates that control, authority, or responsibility is transferred from one entity to another that follows it in a sequence or succession.
- 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_69c0084de39081909eb34e6bed74215a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03c9239e08190bff7ef2bd6d21ae0 |
completed | March 22, 2026, 7:01 p.m. |
| PD | Predicate disambiguation | batch_69c0334412388190bc594794ec5754f9 |
completed | March 22, 2026, 6:21 p.m. |
| PDg | Predicate description generation | batch_69c03c8d579081909d7b97fc9014b5d7 |
completed | March 22, 2026, 7:01 p.m. |
Created at: March 22, 2026, 3:55 p.m.