Triple
T4308457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Transonic Facility |
E94014
|
entity |
| Predicate | pressureCapability |
P56372
|
FINISHED |
| Object | high pressure |
—
|
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: high pressure | Statement: [National Transonic Facility, pressureCapability, high pressure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pressureCapability Context triple: [National Transonic Facility, pressureCapability, high pressure]
-
A.
pressureType
Indicates the specific category or kind of pressure associated with an entity or interaction.
-
B.
pressurization
Indicates the process of applying or maintaining pressure on or within an object, system, or environment.
-
C.
capacityCategory
Indicates the classification of something based on the amount or volume it can hold, handle, or accommodate.
-
D.
pressurizedVolume
Indicates that a specified volume is maintained at a pressure different from ambient (typically higher), often as part of a controlled or sealed system.
-
E.
pumpingPower
Indicates the rate at which energy is supplied or transferred by a pump to move a fluid or medium.
- 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_69b3451886588190a3dd1305ea7c58dc |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b350d2af088190ad7cb035d6e0f8c2 |
completed | March 12, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69b34f4a07b08190a06ada0d9cbb14fb |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b35034cd248190bae09e9d090e13ec |
completed | March 12, 2026, 11:45 p.m. |
Created at: March 12, 2026, 11:11 p.m.