Triple
T34072963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Aero Engines |
E873822
|
entity |
| Predicate | customerSupportBrand |
P34842
|
FINISHED |
| Object | IAE V2500 support network |
—
|
NE NERFINISHED |
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: IAE V2500 support network | Statement: [International Aero Engines, customerSupportBrand, IAE V2500 support network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: customerSupportBrand Context triple: [International Aero Engines, customerSupportBrand, IAE V2500 support network]
-
A.
customerSupport
Indicates that one entity provides assistance, troubleshooting, or service-related help to another entity.
-
B.
supportsBrand
Indicates that one entity endorses, promotes, or is compatible with a particular brand.
-
C.
serviceBrand
chosen
Indicates that one entity is the brand under which a particular service is offered or marketed by another entity.
-
D.
supportStudioCountry
Indicates that a country provides support or backing to a particular studio.
-
E.
parentBrand
Indicates that one brand is the overarching or owning brand from which another brand is derived or subordinated.
- 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_69f349a566808190a1c63b898f33cddf |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:52 a.m.