Triple
T33967812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sud Aviation Caravelle (testbed) |
E870902
|
entity |
| Predicate | engineTypeTested |
P20916
|
FINISHED |
| Object | turbojet engine |
—
|
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: turbojet engine | Statement: [Sud Aviation Caravelle (testbed), engineTypeTested, turbojet engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engineTypeTested Context triple: [Sud Aviation Caravelle (testbed), engineTypeTested, turbojet engine]
-
A.
engineTypeUsed
Indicates that a particular type of engine is employed or utilized in relation to a specified entity or system.
-
B.
testedEngineType
chosen
Indicates that an engine of a specified type has been subjected to a test or evaluation.
-
C.
engineTypeIncluded
Indicates that a specified engine type is included as part of, or supported within, another entity or configuration.
-
D.
engineTypeBuilt
Indicates that a specific type of engine has been constructed or manufactured by a particular entity.
-
E.
engineManufacturerTested
Indicates that an engine manufacturer has been subjected to and has undergone a testing or evaluation process.
- 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_69f3499ce8e88190b66e1d49ad8c7037 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:50 a.m.