Triple
T17593624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District of Columbia Air National Guard |
E428506
|
entity |
| Predicate | establishedInTime |
P9196
|
FINISHED |
| Object | 1946 |
—
|
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: 1946 | Statement: [District of Columbia Air National Guard, establishedInTime, 1946]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedInTime Context triple: [District of Columbia Air National Guard, establishedInTime, 1946]
-
A.
establishedAt
chosen
Indicates the specific time or date at which something (such as an organization, system, or entity) was founded or brought into existence.
-
B.
establishedFrom
Indicates that something was created, founded, or formed starting from a specified source, origin, or prior entity.
-
C.
establishedTo
Indicates that one entity was created, founded, or set up for the purpose of serving, supporting, or enabling another entity.
-
D.
placeEstablished
Indicates that an entity was founded, created, or formally established at a particular place or location.
-
E.
establishedPeriod
Indicates the time span or date range during which something was founded, created, or formally brought into existence.
- 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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e469e89acc81908e52138ad4f452c6 |
completed | April 19, 2026, 5:36 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fff0348190b899a32da537eaca |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:51 a.m.