Triple
T34799572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AJ-60 series |
E1003179
|
entity |
| Predicate | ignitionMode |
P43929
|
FINISHED |
| Object | ground-ignited |
—
|
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: ground-ignited | Statement: [AJ-60 series, ignitionMode, ground-ignited]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ignitionMode Context triple: [AJ-60 series, ignitionMode, ground-ignited]
-
A.
ignitionMethod
chosen
Indicates the specific way or mechanism by which something is ignited or set on fire.
-
B.
ignitionLocation
Indicates the place or setting where an ignition or starting event occurs.
-
C.
ignitionIntegration
Indicates that one system or component is connected to and can interact with another via the Ignition platform or protocol.
-
D.
detonationMode
Indicates the specific manner or mechanism by which a detonation is initiated or carried out in relation to an explosive event.
-
E.
achievedIgnition
Indicates that a process or system has successfully initiated and sustained the intended ignition event or reaction.
- 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77a886ac48190a82b0a71a2092028 |
completed | May 3, 2026, 4:40 p.m. |
| PD | Predicate disambiguation | batch_69f7795b1abc8190823664d1caa94649 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.