Triple
T8217631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orel salient |
E191974
|
entity |
| Predicate | statusBeforeOffensive |
P81544
|
FINISHED |
| Object | German-held bulge in the front line |
—
|
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: German-held bulge in the front line | Statement: [Orel salient, statusBeforeOffensive, German-held bulge in the front line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusBeforeOffensive Context triple: [Orel salient, statusBeforeOffensive, German-held bulge in the front line]
-
A.
statusBeforeWar
Indicates the condition or situation of an entity as it existed prior to the onset of a specified war.
-
B.
politicalStatusBefore
Indicates the political status or condition an entity held prior to a specified event, change, or reference point.
-
C.
status
Indicates the current condition, state, or standing of an entity within a given context.
-
D.
controlledBefore
Indicates that one entity had control or authority over another entity during a time period that occurred earlier than a specified reference time or event.
-
E.
statusLevelAbove
Indicates that one entity’s status level is higher or more advanced than another entity’s status level.
- 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_69ca82c9a8ac81908b011c38698456e4 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb776f41108190bed1c6a8ddbea374 |
completed | March 31, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69cb36ad01ac81909609b15f6a6c8581 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb4ab5162c8190bddd696078689895 |
completed | March 31, 2026, 4:16 a.m. |
Created at: March 30, 2026, 5:45 p.m.