Triple
T27356623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SRB |
E685701
|
entity |
| Predicate | exhaustDirection |
P162221
|
FINISHED |
| Object | through convergent-divergent nozzle |
—
|
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: through convergent-divergent nozzle | Statement: [SRB, exhaustDirection, through convergent-divergent nozzle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exhaustDirection Context triple: [SRB, exhaustDirection, through convergent-divergent nozzle]
-
A.
exhaustType
Indicates the specific kind or configuration of exhaust system associated with an entity.
-
B.
exhaustPosition
Indicates the spatial location or configuration of an exhaust outlet relative to the object it belongs to.
-
C.
exhaustGasTemperature
Indicates the temperature of the exhaust gases produced by an engine or combustion process.
-
D.
turbochargerType
Indicates the specific kind or classification of turbocharger associated with an engine or system.
-
E.
airIntakeType
Indicates the type or configuration of the system or mechanism used to draw air into an engine or device.
- 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_69ef14887c288190931b8431fdbf53c4 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f62c1dec70819087f3f891cb18d6f6 |
completed | May 2, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69f620e4b1c88190a17940251abc68fd |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f621fbfc2c8190bfa802d7dc0f6aa4 |
completed | May 2, 2026, 4:10 p.m. |
Created at: April 27, 2026, 11:51 a.m.