Triple
T10084623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jagdgeschwader 2 |
E215187
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object |
JG 2
JG 2 was a Luftwaffe fighter wing of Nazi Germany during World War II, known for its air combat operations on multiple fronts.
|
E841001
|
NE FINISHED |
How this triple was built (4 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: JG 2 | Statement: [Jagdgeschwader 2, shortName, JG 2]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: JG 2 Context triple: [Jagdgeschwader 2, shortName, JG 2]
-
A.
JG 26
JG 26 was a prominent Luftwaffe fighter wing of Nazi Germany during World War II, noted for its experienced pilots and extensive combat on the Western Front.
-
B.
JG 52
JG 52 was a famed Luftwaffe fighter wing of World War II, notable for including many of Germany’s highest-scoring fighter aces.
-
C.
JG 7
JG 7 was a late-World War II German Luftwaffe fighter wing, notable as the first operational jet fighter unit equipped with the Messerschmitt Me 262.
-
D.
JG 51
JG 51 was a Luftwaffe fighter wing of Nazi Germany during World War II, noted for its extensive operations on the Eastern Front.
-
E.
JG 53
JG 53 was a Luftwaffe fighter wing of Nazi Germany during World War II, noted for its operations on multiple fronts including the Western Front, Eastern Front, and the Mediterranean.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: JG 2 Triple: [Jagdgeschwader 2, shortName, JG 2]
Generated description
JG 2 was a Luftwaffe fighter wing of Nazi Germany during World War II, known for its air combat operations on multiple fronts.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: JG 2 Target entity description: JG 2 was a Luftwaffe fighter wing of Nazi Germany during World War II, known for its air combat operations on multiple fronts.
-
A.
JG 26
JG 26 was a prominent Luftwaffe fighter wing of Nazi Germany during World War II, noted for its experienced pilots and extensive combat on the Western Front.
-
B.
JG 52
JG 52 was a famed Luftwaffe fighter wing of World War II, notable for including many of Germany’s highest-scoring fighter aces.
-
C.
JG 7
JG 7 was a late-World War II German Luftwaffe fighter wing, notable as the first operational jet fighter unit equipped with the Messerschmitt Me 262.
-
D.
JG 51
JG 51 was a Luftwaffe fighter wing of Nazi Germany during World War II, noted for its extensive operations on the Eastern Front.
-
E.
JG 53
JG 53 was a Luftwaffe fighter wing of Nazi Germany during World War II, noted for its operations on multiple fronts including the Western Front, Eastern Front, and the Mediterranean.
- F. None of above. chosen
Provenance (5 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_69ca83a1eed081908b2e9580f2ebeea7 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdd044c1ec8190b5b48cdb0584d00c |
completed | April 2, 2026, 2:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d2b68188c48190ac783cdfc072c502 |
completed | April 5, 2026, 7:22 p.m. |
| NEDg | Description generation | batch_69d2b7aecdb081909f651c1bc1bcfd75 |
completed | April 5, 2026, 7:27 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69d2b86bf8948190a79046efadc4adea |
completed | April 5, 2026, 7:30 p.m. |
Created at: March 30, 2026, 9 p.m.