Triple
T2162194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luftflotte 1 (in air support role) |
E46824
|
entity |
| Predicate | commandRelationship |
P10690
|
FINISHED |
| Object | air component for Army Group North |
—
|
LITERAL 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: air component for Army Group North | Statement: [Luftflotte 1 (in air support role), commandRelationship, air component for Army Group North]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandRelationship Context triple: [Luftflotte 1 (in air support role), commandRelationship, air component for Army Group North]
-
A.
termRelationTo
Indicates a general relational association between one term and another, without specifying the exact nature of that relationship.
-
B.
definesRelationshipBetween
Indicates that one entity specifies or establishes the nature, type, or rules of a relationship that exists between two or more other entities.
-
C.
relationshipType
chosen
Indicates the specific kind of relationship that exists between two or more entities.
-
D.
titleRelation
Indicates a relationship where one entity serves as the title, designation, or formal name associated with another entity.
-
E.
semanticRelation
Indicates a general meaning-based connection between two entities, such as similarity, implication, or conceptual association.
- 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_69a88a184cbc8190877791f6552c2484 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbe8b9c0881908373eabc7f81c394 |
completed | March 7, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_69abbd9c90408190b6b65498ca43ce26 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:45 p.m.