Triple
T171602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vertical Motion Simulator |
E3133
|
entity |
| Predicate | dataOutput |
P4241
|
FINISHED |
| Object | flight dynamics data |
—
|
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: flight dynamics data | Statement: [Vertical Motion Simulator, dataOutput, flight dynamics data]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataOutput Context triple: [Vertical Motion Simulator, dataOutput, flight dynamics data]
-
A.
dataModel
Indicates a relationship where an entity defines, uses, or is structured according to a specific data model or schema.
-
B.
dataStorage
Indicates a relationship where one entity serves as a repository that holds, retains, or maintains data for another entity or process.
-
C.
dataRate
Indicates the rate at which data is transmitted, processed, or transferred between entities over a given time interval.
-
D.
dataUse
Indicates how data is intended to be accessed, processed, or applied within a particular context or activity.
-
E.
dataTypeCollected
chosen
Indicates that a specific type or category of data is gathered or recorded in the context of an entity or process.
- 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_69a2524ce1e48190ab066bf72859f474 |
completed | Feb. 28, 2026, 2:26 a.m. |
| NER | Named-entity recognition | batch_69a25a3f9d188190aacf5791273e2c65 |
completed | Feb. 28, 2026, 3 a.m. |
| PD | Predicate disambiguation | batch_69a25667717c8190bac5108366e2178d |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:34 a.m.