Triple
T38028347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rolls-Royce Peregrine |
E948839
|
entity |
| Predicate | compressionRatioClass |
P189874
|
FINISHED |
| Object | high for its time |
—
|
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: high for its time | Statement: [Rolls-Royce Peregrine, compressionRatioClass, high for its time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compressionRatioClass Context triple: [Rolls-Royce Peregrine, compressionRatioClass, high for its time]
-
A.
compressionRatio
Indicates the proportional reduction in size or volume achieved when something is compressed compared to its original size.
-
B.
compressionType
Indicates the method or format used to compress data or content in the relationship.
-
C.
compressionCharacteristic
Indicates how an entity behaves or performs when subjected to compressive forces or pressure.
-
D.
compressionDirection
Indicates the direction along which a material, object, or signal is being compressed or reduced in size or volume.
-
E.
compressionMode
Indicates the specific method or setting used to compress data or content in a given context.
- F. None of above. chosen
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_69f76efd1bc48190a729097fe5177b61 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbca6c066c8190a1599202f341417f |
completed | May 6, 2026, 11:10 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
| PDg | Predicate description generation | batch_69fbc993caa881908c16c3e21efaeef9 |
completed | May 6, 2026, 11:07 p.m. |
Created at: May 3, 2026, 4:20 p.m.