Triple
T36058847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boeing 777-200ER |
E1043019
|
entity |
| Predicate | thrustRange_lbf |
P184931
|
FINISHED |
| Object | 77000–92000 |
—
|
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: 77000–92000 | Statement: [Boeing 777-200ER, thrustRange_lbf, 77000–92000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thrustRange_lbf Context triple: [Boeing 777-200ER, thrustRange_lbf, 77000–92000]
-
A.
thrustInVacuum_lbf
Indicates the amount of thrust force produced in a vacuum, measured in pounds-force (lbf), by an engine or propulsion system.
-
B.
thrust
Indicates a forceful forward push or drive exerted by one entity onto another or into a particular direction.
-
C.
thrustType
Indicates the type or method of thrust or propulsion used in performing an action or driving a system.
-
D.
thrustDistribution
Indicates how thrust or propulsive force is apportioned or spread among different components, directions, or stages within a system.
-
E.
thrustAtSeaLevel
Indicates the amount of propulsive force an engine produces when operating at standard sea-level atmospheric conditions.
- 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_69f76e2f09448190b0486d5ecad5e243 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69f7b69a74a08190b31b1201278a2c57 |
completed | May 3, 2026, 8:56 p.m. |
Created at: May 3, 2026, 4:08 p.m.