Triple
T33146706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rolls-Royce AE engine core |
E848319
|
entity |
| Predicate | usedInEngineFamily |
P126220
|
FINISHED |
| Object | Rolls-Royce AE family |
—
|
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: Rolls-Royce AE family | Statement: [Rolls-Royce AE engine core, usedInEngineFamily, Rolls-Royce AE family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInEngineFamily Context triple: [Rolls-Royce AE engine core, usedInEngineFamily, Rolls-Royce AE family]
-
A.
belongsToEngineFamily
chosen
Indicates that an engine is a member of, or classified under, a specific engine family or series.
-
B.
usedOnVehicleFamily
Indicates that something is designed or intended to be used on a particular family or category of vehicles.
-
C.
engineUsedIn
Indicates that a particular engine is utilized as a component or power source within a specified system, device, or application.
-
D.
notableEngineFamily
Indicates that one entity is a well-known or significant engine family associated with the other entity.
-
E.
usedInDeviceFamily
Indicates that something (such as a component, technology, or feature) is employed or incorporated within a particular family of related devices.
- 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_69f3495a458c8190a1d34b237ba0be3f |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe349879848190bcd77e3cc3470458 |
completed | May 8, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69fe31e3cf908190b23ebc2f7fe58722 |
completed | May 8, 2026, 6:56 p.m. |
Created at: May 1, 2026, 1:28 a.m.