Triple
T5187278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LAROM multiple rocket launcher |
E117062
|
entity |
| Predicate | launcherConfiguration |
P6754
|
FINISHED |
| Object | modular launcher system |
—
|
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: modular launcher system | Statement: [LAROM multiple rocket launcher, launcherConfiguration, modular launcher system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launcherConfiguration Context triple: [LAROM multiple rocket launcher, launcherConfiguration, modular launcher system]
-
A.
launcherType
chosen
Indicates the specific kind or category of launcher associated with or used in relation to an entity.
-
B.
launchProvider
Indicates that one entity serves as the organization or company responsible for launching another entity (such as a spacecraft, satellite, or mission).
-
C.
launchServiceEntry
Indicates initiating or starting the provision of a particular service or service instance.
-
D.
launchEnvironment
Indicates the specific context, configuration, or setting in which a launch or deployment action takes place.
-
E.
launchLocation
Indicates the place or site from which something is launched or set into motion.
- 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_69bd44620ff48190bcac01782107a397 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd79c3e9e08190848be4208b72f310 |
completed | March 20, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69bd77b7e8b4819092ec3965e11f2dea |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:46 p.m.