Triple
T112482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Canadian Air Force |
E2277
|
entity |
| Predicate | disbanded |
P133
|
FINISHED |
| Object | 1968 |
—
|
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: 1968 | Statement: [Royal Canadian Air Force, disbanded, 1968]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disbanded Context triple: [Royal Canadian Air Force, disbanded, 1968]
-
A.
dissolvedOrAbolished
chosen
Indicates that an organization, institution, or formal entity has been officially terminated, disbanded, or ceased to exist.
-
B.
discontinuedIn
Indicates that an item, product, or service stopped being produced, offered, or supported starting in a specified time or place.
-
C.
dissolved
Indicates that one substance has been mixed into another so thoroughly that it forms a uniform solution and is no longer distinguishable as a separate phase.
-
D.
scrapped
Indicates that something planned, created, or in progress was abandoned, discarded, or cancelled and will no longer be pursued or used.
-
E.
retired
Indicates that an entity has permanently stopped working in their former occupation or role, typically after reaching a certain age or service duration.
- 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.