Triple
T2559986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Max |
E57218
|
entity |
| Predicate | discontinuedAsMilitaryOrder |
P40475
|
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: [Blue Max, discontinuedAsMilitaryOrder, 1918]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discontinuedAsMilitaryOrder Context triple: [Blue Max, discontinuedAsMilitaryOrder, 1918]
-
A.
discontinuedIn
Indicates that an item, product, or service stopped being produced, offered, or supported starting in a specified time or place.
-
B.
discontinuedWith
Indicates that an item, service, or process has been stopped or terminated in association with a particular entity, condition, or context.
-
C.
discontinuedModel
Indicates that a particular model is no longer produced, sold, or officially supported.
-
D.
temporarilyDiscontinued
Indicates that an activity, service, or relationship has been stopped for a limited period but is expected to resume in the future.
-
E.
militaryUseEnd
Indicates the point in time or condition at which the military use of something (such as a facility, resource, or asset) ceases.
- F. None of above. chosen
Provenance (4 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_69ab4a4ef9008190a0e6d4422b9418b7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd35c6ee88190b6eaa1841d3e99a4 |
completed | March 7, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69abd0caeb488190b0dd8e48d0f2777d |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd35b216881908f4ef32d1c1e5080 |
completed | March 7, 2026, 7:27 a.m. |
Created at: March 6, 2026, 9:48 p.m.