Triple
T19904911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JG 51 |
E478387
|
entity |
| Predicate | subunit |
P35
|
FINISHED |
| Object | I./JG 51 |
—
|
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: I./JG 51 | Statement: [JG 51, subunit, I./JG 51]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: I./JG 51 Context triple: [JG 51, subunit, I./JG 51]
-
A.
I./JG 2
I./JG 2 was the first Gruppe (group) of the German Luftwaffe fighter wing Jagdgeschwader 2, operating primarily as a frontline fighter unit during World War II.
-
B.
III./JG 2
III./JG 2 was the third Gruppe (group) of the German Luftwaffe fighter wing Jagdgeschwader 2, active primarily during World War II.
-
C.
II./JG 2
II./JG 2 was the second Gruppe (group) of the German Luftwaffe fighter wing Jagdgeschwader 2, active primarily during World War II.
-
D.
Jagdgeschwader 51
chosen
Jagdgeschwader 51 was a prominent Luftwaffe fighter wing of World War II, noted for its high-scoring aces and extensive operations on the Eastern Front.
-
E.
BSG Einheit Crimmitschau
BSG Einheit Crimmitschau was an East German football club from Crimmitschau that competed in the top-tier DDR-Oberliga during the GDR era.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e520682081909892916424699bd5 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65945cc2081908224902d5f042d7a |
completed | April 20, 2026, 4:50 p.m. |
Created at: April 10, 2026, 1:52 p.m.