Triple
T112379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jagdgeschwader 26 |
E2275
|
entity |
| Predicate | operationalPeriod |
P802
|
FINISHED |
| Object | World War II era |
—
|
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: World War II era | Statement: [Jagdgeschwader 26, operationalPeriod, World War II era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationalPeriod Context triple: [Jagdgeschwader 26, operationalPeriod, World War II era]
-
A.
operatedDuring
chosen
Indicates that an action, process, or system was functioning or in operation throughout a specified time period or event.
-
B.
operatedAt
Indicates that an operation, procedure, or activity was performed at a specific location or facility.
-
C.
operatedFor
Indicates that one entity performed operations or provided services on behalf of, or in support of, another entity for a certain period or purpose.
-
D.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
E.
operatedOn
Indicates that one entity has performed a surgical or procedural operation on 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_69a24fcdaeb48190a2d796677e4b3281 |
completed | Feb. 28, 2026, 2:15 a.m. |
| NER | Named-entity recognition | batch_69a258808ff08190a06b6206f635612b |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a256425a488190959d71e39e699d90 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:20 a.m.