Triple
T32949097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | II./JG 2 |
E842891
|
entity |
| Predicate | gruppeDesignation |
P139721
|
FINISHED |
| Object | II. Gruppe |
—
|
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: II. Gruppe | Statement: [II./JG 2, gruppeDesignation, II. Gruppe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gruppeDesignation Context triple: [II./JG 2, gruppeDesignation, II. Gruppe]
-
A.
clusterDesignation
Indicates that an entity is assigned to or identified as part of a specific cluster or grouping.
-
B.
bdDesignation
Indicates that one entity is formally assigned or designated as having a particular role, status, or classification in relation to another entity.
-
C.
systemDesignation
Indicates that an entity has been assigned a specific formal label or identifier within a defined system or framework.
-
D.
bandDesignation
chosen
Indicates that one entity is formally assigned or labeled as belonging to a particular band, group, or category.
-
E.
collectionDesignation
Indicates that one entity assigns or specifies a particular collection label or designation for another entity.
- 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_69f3494a31f481909057136e49b4fe60 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d141e534819082c755778666c835 |
completed | May 3, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:21 a.m.