Triple
T2115482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamilton Sundstrand |
E43799
|
entity |
| Predicate | providedSystemsFor |
P13398
|
FINISHED |
| Object | commercial airliners |
—
|
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: commercial airliners | Statement: [Hamilton Sundstrand, providedSystemsFor, commercial airliners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providedSystemsFor Context triple: [Hamilton Sundstrand, providedSystemsFor, commercial airliners]
-
A.
supportedSystem
chosen
Indicates that one entity provides compatibility, functionality, or operational support for another system.
-
B.
providedFor
Indicates that one entity supplies, furnishes, or makes something available to or on behalf of another entity for its use or benefit.
-
C.
associatedSystem
Indicates that one entity is functionally or contextually linked to a particular system with which it interacts or to which it belongs.
-
D.
establishedSystem
Indicates that an entity has created, set up, or formally put into operation a particular system or structured arrangement.
-
E.
providesSupportTo
Indicates that one entity offers help, resources, or reinforcement to another entity to aid its function, stability, or success.
- 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_69a88717cfe48190b7ecdd68c824848a |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbb0724e08190a0a4210d86261d6d |
completed | March 7, 2026, 5:43 a.m. |
| PD | Predicate disambiguation | batch_69abb7bbf9d881909d223b0cab7cab18 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.