Triple
T20667705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lightning F.6 |
E507935
|
entity |
| Predicate | afterburning |
P63794
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Lightning F.6, afterburning, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afterburning Context triple: [Lightning F.6, afterburning, yes]
-
A.
AfterburnType
chosen
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.
burningSince
Indicates that an object or substance has been continuously burning from a specified starting time up to the present or another reference time.
-
C.
after
Indicates that one event, state, or action occurs later in time than another, following it in temporal order.
-
D.
burned
Indicates that one entity caused another entity to be damaged or consumed by fire or intense heat.
-
E.
burns
Indicates that one entity is consuming or damaging another through fire or intense heat.
- 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_69e0b4c059bc81908ea762cd73ea4424 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6b5c4c4608190ae17da4a59e5ae80 |
completed | April 20, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69e5c03caee881908be4dd25796a03d5 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 11:44 a.m.