Triple
T456764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pour le Mérite |
E7249
|
entity |
| Predicate | militaryClassDiscontinued |
P1466
|
FINISHED |
| Object | 1918 |
—
|
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: 1918 | Statement: [Pour le Mérite, militaryClassDiscontinued, 1918]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryClassDiscontinued Context triple: [Pour le Mérite, militaryClassDiscontinued, 1918]
-
A.
isMilitaryVariantOf
Indicates that one entity is a military-specific version or adaptation of another, typically civilian or general-purpose, entity.
-
B.
decommissionedReason
Indicates the reason or cause for which an entity, typically an asset or system, was taken out of service or formally retired.
-
C.
discontinuedIn
chosen
Indicates that an item, product, or service stopped being produced, offered, or supported starting in a specified time or place.
-
D.
destructionYear
Indicates the year in which an entity was destroyed or ceased to exist due to destructive events or actions.
-
E.
strickenFromNavalRegister
Indicates that a vessel has been officially removed from a navy’s active register, ending its status as a commissioned naval ship.
- 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_69a2e7e5c5bc8190a1dc8178218fba40 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efa1616481909399f92551a0c9e3 |
completed | Feb. 28, 2026, 1:37 p.m. |
| PD | Predicate disambiguation | batch_69a2ede614b88190be07425f5535f56d |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.