Triple
T32594944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilde Sau tactic |
E833176
|
entity |
| Predicate | implementedByUnit |
P103601
|
FINISHED |
| Object | Jagdgeschwader 300 |
—
|
NE NERFINISHED |
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: Jagdgeschwader 300 | Statement: [Wilde Sau tactic, implementedByUnit, Jagdgeschwader 300]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: implementedByUnit Context triple: [Wilde Sau tactic, implementedByUnit, Jagdgeschwader 300]
-
A.
implementedUnder
Indicates that an action, policy, or process is carried out within the scope, authority, or framework defined by a particular higher-level plan, rule, or governing entity.
-
B.
introducedByUnit
chosen
Indicates that something was brought into existence, initiated, or caused as a result of the actions or influence of a particular unit.
-
C.
areImplementedBy
Indicates that one entity serves as the concrete realization or execution of the specification, design, or interface defined by another entity.
-
D.
currentlyImplementedBy
Indicates that a given specification, design, or feature is presently realized or supported by a particular implementation or system.
-
E.
implementedByAgency
Indicates that an action, program, or policy is carried out or executed by a specific agency.
- 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_69f34929ff648190aded9424aa7564ae |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:05 a.m.