Triple
T33372031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pratt & Whitney Canada |
E854516
|
entity |
| Predicate | servesSegment |
P1670
|
FINISHED |
| Object | regional aviation |
—
|
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: regional aviation | Statement: [Pratt & Whitney Canada, servesSegment, regional aviation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesSegment Context triple: [Pratt & Whitney Canada, servesSegment, regional aviation]
-
A.
servesBrandSegment
Indicates that one entity provides products, services, or offerings specifically targeted to a particular brand segment.
-
B.
operatesInSegment
chosen
Indicates that an entity conducts its activities or provides its services within a specified market or operational segment.
-
C.
servesBranch
Indicates that one entity provides services or support to a particular branch or subdivision of an organization.
-
D.
servesIntersection
Indicates that one entity provides service or operational coverage to a specific road or transit intersection.
-
E.
isServedFor
Indicates that something is provided or presented as suitable or intended for a particular purpose, use, or recipient.
- 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_69f3496ca10c8190908640d18fa00832 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff63225b6481909217ad11b4f7d3ba |
completed | May 9, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69ff60e0882c819085d097010db43ee0 |
completed | May 9, 2026, 4:29 p.m. |
Created at: May 1, 2026, 1:35 a.m.