Triple
T12432997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pratt & Whitney PW6000 |
E297077
|
entity |
| Predicate | applicationCategory |
P45312
|
FINISHED |
| Object | civil turbofan |
—
|
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: civil turbofan | Statement: [Pratt & Whitney PW6000, applicationCategory, civil turbofan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: applicationCategory Context triple: [Pratt & Whitney PW6000, applicationCategory, civil turbofan]
-
A.
apparentCategory
Indicates the category or type that something seems to belong to based on its observable characteristics, regardless of its true or underlying classification.
-
B.
applicationRequirement
Indicates that one entity specifies a condition or prerequisite that must be met for the use, approval, or execution of another entity or process.
-
C.
typeOfApplication
chosen
Indicates the specific category or kind of application involved in the relationship or action.
-
D.
applicationMedium
Indicates the medium or channel through which an application is submitted or communicated (e.g., online, paper, email).
-
E.
commonApplication
Indicates that multiple entities share or participate in the same application, process, or usage context.
- 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_69d6ada0640c81908c061d7fb3d47786 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94df948308190ace333230a4a3b38 |
completed | April 10, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69d94d391c548190996a8c698357f273 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:55 p.m.