Triple
T23457817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TAPS (Twin Annular Pre-mixing Swirler) |
E567979
|
entity |
| Predicate | engineeringDomain |
P77595
|
FINISHED |
| Object | aero-thermal engineering |
—
|
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: aero-thermal engineering | Statement: [TAPS (Twin Annular Pre-mixing Swirler), engineeringDomain, aero-thermal engineering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engineeringDomain Context triple: [TAPS (Twin Annular Pre-mixing Swirler), engineeringDomain, aero-thermal engineering]
-
A.
engineeringBasis
Indicates that something serves as the foundational technical or engineering rationale, justification, or underlying basis for another entity or decision.
-
B.
engineeringEmphasis
Indicates that something places a primary focus or specialization on engineering principles, methods, or activities.
-
C.
typeOfEngineering
chosen
Indicates that one entity is a specific branch, category, or kind of engineering to which the other entity belongs.
-
D.
engineeringContribution
Indicates a relationship where an entity contributes engineering work, expertise, or effort toward the design, development, or improvement of another entity.
-
E.
engineeringDesign
Indicates the relationship in which an entity is responsible for planning, specifying, or creating the technical design of another entity (such as a system, component, or structure).
- 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_69e2458b4c888190b1d7998f9862a558 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a69904588190b44c84021e94ae63 |
completed | April 29, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:53 p.m.