Triple
T36483064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SA-4 |
E898867
|
entity |
| Predicate | engineOutTest |
P177913
|
FINISHED |
| Object | one H-1 engine was intentionally shut down during flight |
—
|
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: one H-1 engine was intentionally shut down during flight | Statement: [SA-4, engineOutTest, one H-1 engine was intentionally shut down during flight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engineOutTest Context triple: [SA-4, engineOutTest, one H-1 engine was intentionally shut down during flight]
-
A.
testedEngine
chosen
Indicates that an engine has undergone a testing process to evaluate its performance, functionality, or reliability.
-
B.
testedEngineType
Indicates that an engine of a specified type has been subjected to a test or evaluation.
-
C.
outputOf
Indicates that one entity is the result or product generated by the processing, operation, or behavior of another entity.
-
D.
engineManufacturerTested
Indicates that an engine manufacturer has been subjected to and has undergone a testing or evaluation process.
-
E.
engineName
Indicates the specific name assigned to an engine associated with an entity.
- 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_69f76e5a0e088190a2b6706aeb41723c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:10 p.m.