Triple
T19042259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army Group C |
E466033
|
entity |
| Predicate | laterTask |
P134851
|
FINISHED |
| Object | overall command of German forces in Italy |
—
|
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: overall command of German forces in Italy | Statement: [Army Group C, laterTask, overall command of German forces in Italy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterTask Context triple: [Army Group C, laterTask, overall command of German forces in Italy]
-
A.
laterWork
Indicates that one work was created, published, or produced after another work in time.
-
B.
laterWorkBy
Indicates that one work was created after another work by the same creator or author.
-
C.
laterIn
Indicates that one event, state, or time point occurs after another in temporal order.
-
D.
laterFunction
Indicates that one function or event occurs after another in time.
-
E.
laterWithin
Indicates that one event or time point occurs later than another while still falling within a specified temporal interval or boundary.
- 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_69d8dd0359648190bc2a9202c5cf29d2 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d801ef188190a231e85e1bbce037 |
completed | April 20, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69e4b99633c8819097988608c278ecf8 |
completed | April 19, 2026, 11:16 a.m. |
| PDg | Predicate description generation | batch_69e4c0fc3c4c8190abbfe06e1bd3325c |
completed | April 19, 2026, 11:48 a.m. |
Created at: April 10, 2026, 12:03 p.m.