Triple
T545727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eurojet EJ200 |
E12727
|
entity |
| Predicate | hasUpgradePath |
P5357
|
FINISHED |
| Object | EJ2x0 growth variants |
—
|
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: EJ2x0 growth variants | Statement: [Eurojet EJ200, hasUpgradePath, EJ2x0 growth variants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUpgradePath Context triple: [Eurojet EJ200, hasUpgradePath, EJ2x0 growth variants]
-
A.
hasUpgrade
chosen
Indicates that one entity possesses, includes, or is associated with an improved or enhanced version of another entity.
-
B.
upgradeEligibility
Indicates whether an entity qualifies to move from its current version, level, or plan to a higher or more advanced one under defined criteria.
-
C.
plannedUpgrade
Indicates that an entity has a scheduled or intended improvement or enhancement to be carried out in the future.
-
D.
hasMigrationHistoryFrom
Indicates that an entity has a recorded history of migrating or moving from a specified origin location or source.
-
E.
hasHigherClass
Indicates that one entity belongs to a higher rank, level, or category in a hierarchy than another entity.
- 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_69a49334226c81908b0ea1689ef6aa3f |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a498dfec5c81908b76d723b30dc2f0 |
completed | March 1, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69a494b957988190bc269e372df2f0b2 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.