Triple
T28853670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jagdstaffel 26 |
E728673
|
entity |
| Predicate | aceProduced |
P165664
|
FINISHED |
| Object | Bruno Loerzer |
—
|
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: Bruno Loerzer | Statement: [Jagdstaffel 26, aceProduced, Bruno Loerzer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aceProduced Context triple: [Jagdstaffel 26, aceProduced, Bruno Loerzer]
-
A.
producedAs
Indicates that one entity is created, generated, or brought into existence as a result or output of another entity or process.
-
B.
producedSaint
Indicates that an entity (such as a place, group, or lineage) has given rise to or brought forth a particular saint.
-
C.
producedRecording
Indicates that one entity served as the producer responsible for creating or overseeing the making of a particular recording.
-
D.
produces
Indicates that one entity creates, generates, or yields another entity as a result or output.
-
E.
isSoundProducedBy
Indicates that a particular sound is generated or emitted by a specified source or entity.
- 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_69f0319f4e5481909e4c439dbe8be940 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f659db52f48190a610183087d3b39d |
completed | May 2, 2026, 8:08 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f658ebeca4819096beb3f98f73fe31 |
completed | May 2, 2026, 8:05 p.m. |
Created at: April 28, 2026, 6:44 a.m.