Triple
T201338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ames Research Center 80-by-120-Foot Wind Tunnel |
E4510
|
entity |
| Predicate | flowType |
P8232
|
FINISHED |
| Object | subsonic |
—
|
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: subsonic | Statement: [Ames Research Center 80-by-120-Foot Wind Tunnel, flowType, subsonic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flowType Context triple: [Ames Research Center 80-by-120-Foot Wind Tunnel, flowType, subsonic]
-
A.
flowsPast
Indicates that one entity (typically a fluid or river) moves in a continuous stream alongside and beyond another entity, passing by its location.
-
B.
outflow
Indicates the movement or discharge of something from an origin or source to the outside or to another location.
-
C.
flowControl
Indicates a relationship where one entity regulates, directs, or manages the rate or sequence of another entity’s operations or movement.
-
D.
dropType
Indicates the manner or category of how something is dropped, released, or caused to fall.
-
E.
trafficType
Indicates the category or nature of traffic involved in a given interaction, flow, or connection (e.g., type of network, data, or transport traffic).
- 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_69a25737567c81908f9c505300239181 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25c2ead8481909996042efcae5e9d |
completed | Feb. 28, 2026, 3:08 a.m. |
| PD | Predicate disambiguation | batch_69a25b4a0d448190a6fa6aeb30dc7e13 |
completed | Feb. 28, 2026, 3:04 a.m. |
| PDg | Predicate description generation | batch_69a25c2bda788190bcfc0bc94686f9e0 |
completed | Feb. 28, 2026, 3:08 a.m. |
Created at: Feb. 28, 2026, 2:51 a.m.