Triple
T11989464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tupolev Tu-160 |
E285366
|
entity |
| Predicate | designStarted |
P102750
|
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: [Tupolev Tu-160, designStarted, 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designStarted Context triple: [Tupolev Tu-160, designStarted, 1970s]
-
A.
designStatus
Indicates the current state or phase of progress for a design within its lifecycle.
-
B.
designLead
Indicates that one entity serves as the primary designer or person in charge of leading the design work for another entity or project.
-
C.
designProcess
Indicates the sequence of actions, decisions, and iterations involved in creating, developing, or refining a design.
-
D.
draftingStarted
Indicates that the process of creating an initial version or draft of something has begun.
-
E.
designUse
Indicates that one entity is used as a design basis, purpose, or intended functional use for another entity.
- F. None of above. chosen
Provenance (4 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_69d6ab44a77c8190a652f4b27164e4ef |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903afe4388190a2cf2328e85adf9b |
completed | April 10, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69d902abca70819098291aa51b593708 |
completed | April 10, 2026, 2:01 p.m. |
| PDg | Predicate description generation | batch_69d903a8695c8190bfa9d7ca50834f9f |
completed | April 10, 2026, 2:05 p.m. |
Created at: April 8, 2026, 9:46 p.m.