Triple
T30840574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Embraer Phenom 100 |
E785495
|
entity |
| Predicate | powerplantThrustPerEngine |
P123904
|
FINISHED |
| Object | 1695 lbf |
—
|
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: 1695 lbf | Statement: [Embraer Phenom 100, powerplantThrustPerEngine, 1695 lbf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerplantThrustPerEngine Context triple: [Embraer Phenom 100, powerplantThrustPerEngine, 1695 lbf]
-
A.
thrustPerEngine
chosen
Indicates the amount of thrust produced by each individual engine in a multi-engine system.
-
B.
powerplantThrustClass
Indicates the classification of a powerplant based on the level or range of thrust it produces.
-
C.
totalThrust
Indicates the combined amount of thrust produced by one or more propulsion sources acting on an object or system.
-
D.
thrustAugmentationMethod
Indicates the method or technique used to increase or enhance thrust in a propulsion system.
-
E.
enginePower
Indicates the power output produced by an engine, typically quantifying its capability to perform work or generate mechanical energy.
- 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_69f224b73d8c81908129383bfb397c87 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 29, 2026, 8:45 p.m.