Triple
T1397889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASME International Gas Turbine Institute |
E30709
|
entity |
| Predicate | TurboExpo_focus |
P11311
|
FINISHED |
| Object | gas turbines |
—
|
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: gas turbines | Statement: [ASME International Gas Turbine Institute, TurboExpo_focus, gas turbines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: TurboExpo_focus Context triple: [ASME International Gas Turbine Institute, TurboExpo_focus, gas turbines]
-
A.
turbochargedVariant
Indicates that one entity is a turbocharged version or configuration of another entity.
-
B.
turbineType
chosen
Indicates the specific kind or category of turbine associated with or used by an entity.
-
C.
notableEngineType
Indicates that an entity is particularly recognized for using or being associated with a specific type of engine.
-
D.
technologyTrend
Indicates a relationship where a technology is characterized as part of a broader pattern of change or direction in technological development over time.
-
E.
propulsionFeature
Indicates a relationship where a propulsion-related characteristic or capability is attributed to an 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_69a498fd4e408190bd73eca30ea9754c |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c382b6588190833c39ac84fb6139 |
completed | March 1, 2026, 10:53 p.m. |
| PD | Predicate disambiguation | batch_69a4bf017f8081908572121560ec621f |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.