Triple
T35041039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Light Helicopter Turbine Engine Company |
E1011070
|
entity |
| Predicate | notableEngineApplication |
P198670
|
FINISHED |
| Object | AgustaWestland AW159 Wildcat |
E312486
|
NE 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: AgustaWestland AW159 Wildcat | Statement: [Light Helicopter Turbine Engine Company, notableEngineApplication, AgustaWestland AW159 Wildcat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEngineApplication Context triple: [Light Helicopter Turbine Engine Company, notableEngineApplication, AgustaWestland AW159 Wildcat]
-
A.
notableApp
Indicates that an application is recognized as significant, prominent, or noteworthy in some context.
-
B.
notableEngineType
Indicates that an entity is particularly recognized for using or being associated with a specific type of engine.
-
C.
notableSystem
Indicates that a system is recognized as significant, prominent, or noteworthy in a particular context or domain.
-
D.
notablyAppliedIn
chosen
Indicates that something is prominently or especially used, implemented, or practiced within a particular context, field, or situation.
-
E.
notableApplicationDevelopedOn
Indicates that a notable software application was created or built to run on a particular platform, system, or technology.
- F. None of above.
Provenance (4 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_69f76dcea02c81908542a223f6d5059f |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37bd30ecfc81908d9b14c44901d297 |
completed | June 21, 2026, 10:30 a.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:01 p.m.