Triple
T7979487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Defense Command |
E185530
|
entity |
| Predicate | dateRedesignated |
P73142
|
FINISHED |
| Object | 1948-12-01 |
—
|
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: 1948-12-01 | Statement: [Air Defense Command, dateRedesignated, 1948-12-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateRedesignated Context triple: [Air Defense Command, dateRedesignated, 1948-12-01]
-
A.
redesignationYear
chosen
Indicates the year in which something was officially redesignated, renamed, or assigned a new status or classification.
-
B.
rededicationDate
Indicates the date on which something is formally dedicated again, typically after restoration, change, or renewal.
-
C.
redenominationDate
Indicates the date on which a currency or financial instrument undergoes a formal change in its nominal value or unit (redenomination).
-
D.
designationBegan
Indicates the point in time when a particular designation, title, or status for an entity first became effective.
-
E.
designationDate
Indicates the date on which an entity is formally assigned, designated, or given a particular status or role.
- 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_69ca829851908190b4e03829353ee7c3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3c261904819086910898071f3629 |
completed | March 31, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69cb048009a08190b4c577208a9f8f76 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:14 p.m.