Triple
T17263480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Blücher–Yorck |
E419062
|
entity |
| Predicate | frontlineAdvance |
P126780
|
FINISHED |
| Object | approximately 20 miles |
—
|
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: approximately 20 miles | Statement: [Operation Blücher–Yorck, frontlineAdvance, approximately 20 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frontlineAdvance Context triple: [Operation Blücher–Yorck, frontlineAdvance, approximately 20 miles]
-
A.
frontLine
Indicates that an entity is positioned at or associated with the foremost or primary line of engagement, activity, or defense relative to others.
-
B.
frontLineFeature
Indicates that the subject is a prominent or leading characteristic that stands out at the forefront relative to others.
-
C.
frontlineCommand
Indicates a command relationship where one entity directs or controls operations at the front line of an activity, conflict, or mission.
-
D.
frontLineDuring
Indicates that an entity is positioned at or serves on the front line during a specified time or event.
-
E.
frontlineUse
Indicates that something is used as the primary or first-line option in addressing a problem, condition, or situation.
- 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_69d886d9ab108190b70edd8d17aa1204 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42f4379848190add32ba8e5f93527 |
completed | April 19, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69e3832a284481908a8a3da7ac91de5a |
completed | April 18, 2026, 1:12 p.m. |
| PDg | Predicate description generation | batch_69e39c2fedb881908bfed2c3e5f2616a |
completed | April 18, 2026, 2:58 p.m. |
Created at: April 10, 2026, 5:40 a.m.