Triple
T16021854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GBU-51 JDAM |
E388618
|
entity |
| Predicate | isLaunchedFrom |
P23637
|
FINISHED |
| Object | aircraft |
—
|
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: aircraft | Statement: [GBU-51 JDAM, isLaunchedFrom, aircraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLaunchedFrom Context triple: [GBU-51 JDAM, isLaunchedFrom, aircraft]
-
A.
launchedVia
Indicates that an entity is initiated, deployed, or started by means of a specified method, mechanism, or intermediary.
-
B.
isDeployedFrom
chosen
Indicates that one entity originates, is launched, or put into operation from another specified source or location.
-
C.
launchedWith
Indicates that one entity was initiated, started, or set into motion together with another entity as part of the same launch event.
-
D.
launchedUnder
Indicates that one entity was initiated, started, or brought into operation under the authority, auspices, or framework of another entity (such as a program, organization, or policy).
-
E.
launchesFrom
Indicates that an object or agent initiates its movement, operation, or departure starting at a specified location or source.
- 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_69d86dabcb7c8190b6a39d6831d2fa1b |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1858a00888190b8505071575dc56f |
completed | April 17, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e1826a4f7c8190aba6d4f1075141b0 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:55 a.m.