Triple
T24085909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rolls-Royce AE 1107C-Liberty |
E596641
|
entity |
| Predicate | notableOperatorPlatform |
P155030
|
FINISHED |
| Object | CV-22B Osprey |
—
|
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: CV-22B Osprey | Statement: [Rolls-Royce AE 1107C-Liberty, notableOperatorPlatform, CV-22B Osprey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableOperatorPlatform Context triple: [Rolls-Royce AE 1107C-Liberty, notableOperatorPlatform, CV-22B Osprey]
-
A.
notablePlatformStatus
Indicates that an entity holds a distinguished or officially recognized status on a particular platform.
-
B.
notableSupport
Indicates that one entity provides significant, recognized backing, endorsement, or assistance to another.
-
C.
notableModelOnPlatform
Indicates that a particular model is recognized as notable or prominent on a given platform.
-
D.
platforms
Indicates that one entity provides or serves as a base, medium, or environment that supports the operation, distribution, or presentation of another entity.
-
E.
notableOperationType
Indicates that an entity is associated with a specific type or category of operation that is considered notable or significant.
- 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_69e288c4638c81909bacc28a1e3d436b |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dc2a76c881908ee6e599dc6d155e |
completed | April 29, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
| PDg | Predicate description generation | batch_69f17b58012c81909106b332db399023 |
completed | April 29, 2026, 3:30 a.m. |
Created at: April 17, 2026, 10:44 p.m.