Triple
T22134353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BE-4 |
E546986
|
entity |
| Predicate | replacesEngineClass |
P50109
|
FINISHED |
| Object | hydrocarbon booster engines |
—
|
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: hydrocarbon booster engines | Statement: [BE-4, replacesEngineClass, hydrocarbon booster engines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacesEngineClass Context triple: [BE-4, replacesEngineClass, hydrocarbon booster engines]
-
A.
replacedClass
Indicates that one class has been superseded or substituted by another class, typically in a versioning or refactoring context.
-
B.
engineClass
chosen
Indicates the classification or type category assigned to an engine within a given system or context.
-
C.
renderingEngineReplacedBy
Indicates that one rendering engine has been superseded or substituted by another rendering engine.
-
D.
replacesComponentOf
Indicates that one entity takes the place of a specific component within another entity, substituting for that component in its role or function.
-
E.
replacedPlatform
Indicates that one platform has been superseded or taken over by another platform.
- 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_69e11e39bf348190b541bfa16a7b71e0 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129b8f4248190b6342c8d00942c25 |
completed | April 28, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:32 p.m.