Triple
T233153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German 6th Army |
E4450
|
entity |
| Predicate | finalPhase |
P5784
|
FINISHED |
| Object | retreat toward Germany |
—
|
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: retreat toward Germany | Statement: [German 6th Army, finalPhase, retreat toward Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalPhase Context triple: [German 6th Army, finalPhase, retreat toward Germany]
-
A.
finalStep
Indicates that an action or state represents the last step or concluding stage in a process or sequence.
-
B.
finalDisposition
Indicates the ultimate outcome, status, or resolution assigned to an entity after all relevant processes or decisions are complete.
-
C.
finalCity
Indicates that a given city is the last or ultimate city associated with an entity within a sequence, process, or journey.
-
D.
mainPhase
Indicates that an event, action, or state occurs during the primary or central phase of a larger process or sequence.
-
E.
phase
chosen
Indicates that one entity is in a particular stage, step, or phase within a process, sequence, or lifecycle relative to another reference.
- 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_69a257363ffc81909757bde7ab3404da |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25f14f72081908182e76300b59358 |
completed | Feb. 28, 2026, 3:20 a.m. |
| PD | Predicate disambiguation | batch_69a25b5c8c888190b5544e687736b373 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.