Triple
T15764925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | F-16 program |
E382194
|
entity |
| Predicate | productionStarted |
P60072
|
FINISHED |
| Object | 1970s |
—
|
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: 1970s | Statement: [F-16 program, productionStarted, 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productionStarted Context triple: [F-16 program, productionStarted, 1970s]
-
A.
productionStartApproximate
Indicates that the start of production for something is known only approximately rather than as an exact date or time.
-
B.
preProductionUseStart
Indicates the point in time when something begins being used in a pre-production or testing environment.
-
C.
productionEnd
Indicates that a production process, activity, or run has come to its completion or final stopping point.
-
D.
enteredSeriesProduction
Indicates that an item has transitioned from development or prototype status into regular, large-scale manufacturing or series production.
-
E.
beganCommercialProduction
chosen
Indicates that an entity started producing something commercially, marking the commencement of its large-scale or market-oriented production.
- 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_69d86da09a10819082fe9797b23e4664 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e050b8154881908afe5191e6424f15 |
completed | April 16, 2026, 3 a.m. |
| PD | Predicate disambiguation | batch_69e00531e7ac8190a4190cce4f7fab4c |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:47 a.m.