Triple
T1750359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fighter Wing 52 |
E38424
|
entity |
| Predicate | hasNickname |
P39
|
FINISHED |
| Object | JG 52 |
E38425
|
NE 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: JG 52 | Statement: [Fighter Wing 52, hasNickname, JG 52]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: JG 52 Context triple: [Fighter Wing 52, hasNickname, JG 52]
-
A.
JG 52
chosen
JG 52 was a famed Luftwaffe fighter wing of World War II, notable for including many of Germany’s highest-scoring fighter aces.
-
B.
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.
-
C.
KG 53
KG 53 was a Luftwaffe bomber wing of Nazi Germany during World War II, known for its operations on both the Eastern and Western Fronts.
-
D.
GJ-3
GJ-3 is the regional vehicle registration code assigned to the city of Rajkot in the Indian state of Gujarat.
-
E.
Suter
Suter is a surname of Germanic origin, often associated with individuals of Swiss or German heritage.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a8862bdb2081908aefe831c8aa8017 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69aa64108a208190ae7190065818e42c |
completed | March 6, 2026, 5:20 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ada989b368819098b788d099f2f8e4 |
completed | March 8, 2026, 4:53 p.m. |
Created at: March 4, 2026, 7:31 p.m.