Triple
T8749382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terminal High Altitude Area Defense |
E207916
|
entity |
| Predicate | testProgramStartDate |
P67354
|
FINISHED |
| Object | 1995 |
—
|
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: 1995 | Statement: [Terminal High Altitude Area Defense, testProgramStartDate, 1995]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testProgramStartDate Context triple: [Terminal High Altitude Area Defense, testProgramStartDate, 1995]
-
A.
previewStartDate
Indicates the date and time when a preview period for something begins.
-
B.
startDate
Indicates the point in time when an event, state, or relationship begins.
-
C.
experimentProgramStart
chosen
Indicates the point in time or event at which an experiment program is initiated or begins execution.
-
D.
startDateAsGuerrilla
Indicates the date on which an entity began operating or acting in a guerrilla capacity.
-
E.
estimatedStartDate
Indicates the date on which something is expected or planned to begin, based on current information or projections.
- 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_69ca835bb2bc819084bb5906cb6ef7f8 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5da4214881908b6917f847c43cb5 |
completed | March 31, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69cc5c160dac8190b4aeb4bf0529de52 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:39 p.m.