Triple
T25341812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | F118 |
E635432
|
entity |
| Predicate | afterburner |
P15531
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [F118, afterburner, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afterburner Context triple: [F118, afterburner, no]
-
A.
AfterburnType
Indicates that one event, state, or process occurs as a subsequent or follow-up phase (an "afterburn") relative to another, typically extending or intensifying its effects.
-
B.
hasAfterburner
chosen
Indicates that one entity is equipped with, or possesses, an afterburner system in relation to another entity or context.
-
C.
underFire
Indicates that an entity is being attacked, heavily criticized, or subjected to intense pressure by another entity or group.
-
D.
backblast
Indicates the backward-directed blast or pressure effect produced as a result of an explosive discharge or propulsion event.
-
E.
after
Indicates that one event, state, or action occurs later in time than another, following it in temporal order.
- 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_69e75a99bd6481909476115b35b9a8e4 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f498b818008190a4240a7a2cbeedfd |
completed | May 1, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 1:32 p.m.