Triple
T33967811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sud Aviation Caravelle (testbed) |
E870902
|
entity |
| Predicate | primaryTestedEngine |
P177913
|
FINISHED |
| Object | Rolls-Royce Olympus |
E248442
|
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: Rolls-Royce Olympus | Statement: [Sud Aviation Caravelle (testbed), primaryTestedEngine, Rolls-Royce Olympus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryTestedEngine Context triple: [Sud Aviation Caravelle (testbed), primaryTestedEngine, Rolls-Royce Olympus]
-
A.
testedEngine
chosen
Indicates that an engine has undergone a testing process to evaluate its performance, functionality, or reliability.
-
B.
testedEngineType
Indicates that an engine of a specified type has been subjected to a test or evaluation.
-
C.
mainEnginesInstalled
Indicates that the primary engines have been fitted and secured onto the relevant system or structure.
-
D.
intendedEngineType
Indicates that an entity is designed or specified to use a particular type of engine.
-
E.
testedOn
Indicates that an entity has been used as the subject or material in a test, experiment, or evaluation performed by another entity.
- 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_69f3499ce8e88190b66e1d49ad8c7037 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36f9abe3b48190836c1863707c49b3 |
completed | June 20, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:50 a.m.