Triple
T30708012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PW5000 |
E781805
|
entity |
| Predicate | hasAfterburningCapability |
P15531
|
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: [PW5000, hasAfterburningCapability, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAfterburningCapability Context triple: [PW5000, hasAfterburningCapability, yes]
-
A.
hasAfterburnerOption
Indicates that an entity offers or is equipped with an optional afterburner capability.
-
B.
hasAfterburner
chosen
Indicates that one entity is equipped with, or possesses, an afterburner system in relation to another entity or context.
-
C.
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.
-
D.
isBurning
Indicates that an entity is currently on fire or undergoing combustion.
-
E.
hasBurnUnit
Indicates that one entity (typically a medical facility) includes or is equipped with a specialized unit dedicated to the treatment and care of burn patients.
- 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_69f224abfcf081909492e64d3cc35262 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:35 p.m.