Triple
T24812078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SA-3 Goa |
E620816
|
entity |
| Predicate | typicalBatteryComposition |
P170927
|
FINISHED |
| Object | multiple launchers |
—
|
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: multiple launchers | Statement: [SA-3 Goa, typicalBatteryComposition, multiple launchers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBatteryComposition Context triple: [SA-3 Goa, typicalBatteryComposition, multiple launchers]
-
A.
batteryComposition
Indicates the relationship specifying which materials or chemical components make up a given battery.
-
B.
batteryType
Indicates the specific kind or category of battery associated with or used by an entity.
-
C.
secondaryBatteryType
Indicates the type or category of a secondary (backup or auxiliary) battery associated with an entity.
-
D.
mainBatteryArrangement
Indicates how the primary set of main batteries or main guns are positioned, configured, or distributed relative to the platform they are mounted on.
-
E.
secondaryBattery
Indicates that an entity has a secondary battery system or backup power source in addition to its primary battery.
- F. None of above. chosen
Provenance (4 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_69e2fabfd4648190bd0e5c7f4dbb6cab |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f6984bb55c8190862eb8796868d188 |
completed | May 3, 2026, 12:35 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
| PDg | Predicate description generation | batch_69f6978ec27c8190a488e1f9c2566d38 |
completed | May 3, 2026, 12:32 a.m. |
Created at: April 18, 2026, 4:50 a.m.