Triple
T19483727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | F404-GE-100 |
E487455
|
entity |
| Predicate | hasCompressorType |
P32743
|
FINISHED |
| Object | axial-flow |
—
|
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: axial-flow | Statement: [F404-GE-100, hasCompressorType, axial-flow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompressorType Context triple: [F404-GE-100, hasCompressorType, axial-flow]
-
A.
hasCompressor
Indicates that one entity is equipped with, contains, or uses a compressor associated with it.
-
B.
compressorType
chosen
Indicates the specific kind or category of compressor associated with an entity.
-
C.
supportsCompressedFiles
Indicates that one entity is capable of handling, reading, or working with files that are stored in a compressed format.
-
D.
hasPackageType
Indicates that an entity is associated with or classified under a particular type or category of package.
-
E.
hasTypeOfSupport
Indicates that one entity provides or is associated with a particular kind or category of support in relation to another entity.
- 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_69d8e8d924388190b847cb15bb3d0aff |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6343c23308190a35f462f95338651 |
completed | April 20, 2026, 2:12 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7883308190b73912a71a35a835 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:39 p.m.