Triple
T35601914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Barbarossa (Central sector) |
E1028780
|
entity |
| Predicate | codenameRelation |
P32834
|
FINISHED |
| Object | central axis of Operation Barbarossa |
—
|
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: central axis of Operation Barbarossa | Statement: [Operation Barbarossa (Central sector), codenameRelation, central axis of Operation Barbarossa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codenameRelation Context triple: [Operation Barbarossa (Central sector), codenameRelation, central axis of Operation Barbarossa]
-
A.
codebaseRelation
Indicates a relationship between codebases, such as dependency, derivation, or other structural or functional linkage between them.
-
B.
codenameContext
Indicates that an entity is associated with or used as a codename within a particular contextual scope or situation.
-
C.
codenameComponent
Indicates that one entity serves as the codename or code-designation assigned to another entity as its component or identifying label.
-
D.
codenameOwner
Indicates that one entity is the designated owner or holder of the specified codename associated with another entity.
-
E.
relatedCodename
chosen
Indicates that one entity has an associated or connected codename that is contextually related to it.
- 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_69f76e0598dc8190a6a093e904b9aa70 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79ec355048190af30123ceb6efa2b |
completed | May 3, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.